Hide Forgot
Description of problem: Odd problem, odd symptoms - after some random duration of time (usually after the system is idling several hours) different stuff starts to behave odd. Launching gnome-terminal from the launcher panel becomes impossible - actually it looks like it's trying to start it but after some seconds it just disappears from the taskbar and never actually pops up a terminal window. Second symptom: none of the VPN connections configured in NetworkManager will initiate. Third symptom: IBM Lotus Mobility Client will present some very ugly fonts (like it switches from gtk to qt?) with some old KDE fonts?! Sorry if this doesn't make any sense but I tried starting gnome-terminal from xterm and I get: $ gnome-terminal Failed to summon the GConf demon; exiting. Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a syst em crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Server ping error: IDL:omg.org/CORBA/COMM_FAILURE:1.0) REBOOTING THE COMPUTER WILL TEMPORARILY FIX ALL OF THESE ISSUES. Version-Release number of selected component (if applicable): $ rpm -qva |grep -i gconf GConf2-devel-2.31.91-1.fc14.x86_64 pulseaudio-module-gconf-0.9.21-7.fc14.x86_64 GConf2-gtk-2.31.91-1.fc14.x86_64 gconfmm26-2.28.2-1.fc14.x86_64 GConf2-2.31.91-1.fc14.i686 GConf2-2.31.91-1.fc14.x86_64 pkgconfig-0.25-2.fc14.x86_64 gnome-python2-gconf-2.28.1-3.fc14.x86_64 ruby-gconf2-0.90.4-1.0.fc14.x86_64 How reproducible: I just leave my computer idling for a few hours (overnight often) with BOINC running or not... or some other application even gnome-terminal. If i close gnome-terminal and start to run it again it will fail. NetworkManger / VPN will fail too, etc. Steps to Reproduce: 1. running gnome-terminal 2. start VPN connection from NetworkManager 3. Actual results: 1. Failed to summon the GConf demon; exiting. Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a syst em crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Server ping error: IDL:omg.org/CORBA/COMM_FAILURE:1.0) 2. VPN will not start Expected results: gnome-terminal should start up NetworkManger VPN should start VPN connections IBM LMC should not change UI appearance and not get ugly fonts Additional info: I suppose this issue appeared after some updates were applied or computer forcibly rebooted cause of "swap-paralysis". Fedora 14 x86_64 with IBM OC Fedora layer - always up to date uname -a Linux host 2.6.35.13-91.fc14.x86_64 #1 SMP Tue May 3 13:23:06 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux
This message is a notice that Fedora 14 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 14. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '14' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 14 reached end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping