GNOME Bugzilla – Bug 123389
Issues running gedit after Gnome 2.4 install using garnome
Last modified: 2009-08-15 18:40:50 UTC
I've installed Gnome 2.4 into the /opt/garnome folder on my laptop. The system seems to be running fine except for gedit. When I try to run gedit nothing seems to happen. I then I tried running gedit from a terminal window, and I get the following output: bash-2.05b$ gedit ** (gedit:1192): WARNING **: FIXME: Need to shutdown linc connections ... ** (gedit:1192): WARNING **: CORBA_ORB_destroy: ORB still has 3 refs. ** (gedit:1192): WARNING **: ORB: a total of 28 refs to ORB objects were leaked I am then dropped back to the terminal prompt. I was advised on the Garnome mailing list that this could be an ORBit issue, so I re-installed the ORBit and linc packages (then gedit) but am still getting the same results. System is as follows: Dell Inspiron 8200 laptop 2GHz, 512MB ram, 40GB free hard disk space. Running a Linux From Scratch linux build with: glibc 2.3.2 kernel 2.4.21 and have had no previous GNOME installation prior to using Garnome 0.27.1 to install Gnome into /opt Gedit is version 2.4.0 ORBit2 is version 2.8.1 linc is version 1.1.1 All other apps seem to be running ok, but I asked on the Garnome mailing list if anyone else was having this issue and got no responses. If you need any more information please mail me. Thanks for your time, Mark
I've tried running a trace using gdb (thanks Jens) but I don't think the output is particularly helpful. It's as follows: (gdb) run Starting program: /opt/garnome/bin/gedit [New Thread 16384 (LWP 1185)] ** (gedit:1185): WARNING **: FIXME: Need to shutdown linc connections ... ** (gedit:1185): WARNING **: CORBA_ORB_destroy: ORB still has 3 refs. ** (gedit:1185): WARNING **: ORB: a total of 28 refs to ORB objects were leaked Program exited normally. (gdb) thread apply all bt Cannot find new threads: generic error (gdb) thread apply 16384 bt warning: Unknown thread 16384. (gdb) The output seems to suggest that I've quit gedit somehow, but it never gets as far as presenting a window on-screen.
I've been doing some more searching and have found the following in my user.log file: Sep 28 11:48:56 mw gconfd (mw-5511): starting (version 2.4.0.1), pid 5511 user 'mw' Sep 28 11:48:56 mw gconfd (mw-5511): Resolved address "xml:readonly:/opt/garnome/etc/gconf/gconf.xml.mandatory" to a read-only config source at position 0 Sep 28 11:48:56 mw gconfd (mw-5511): Resolved address "xml:readwrite:/home/mw/.gconf" to a writable config source at position 1 Sep 28 11:48:56 mw gconfd (mw-5511): Resolved address "xml:readonly:/opt/garnome/etc/gconf/gconf.xml.defaults" to a read-only config source at position 2 Sep 28 11:49:49 mw gconfd (mw-5511): Received signal 1, shutting down cleanly Sep 28 11:49:49 mw gconfd (mw-5511): Exiting Sep 28 11:49:49 mw gconfd (mw-5511): FIXME: Need to shutdown linc connections ... Sep 28 11:49:49 mw gconfd (mw-5511): CORBA_ORB_destroy: ORB still has 2 refs. Sep 28 11:49:49 mw gconfd (mw-5511): ORB: a total of 18 refs to ORB objects were leaked Is the above all as it should be? The entries timed at 11:49:49 are entries at the point that I closed GNOME down, I thought it might help to track my problem down because the warnings given are identical to the ones I get when I try to run gedit. Could running gedit be stopping the GConf daemon somehow?
Try to run gedit --debug from a terminal. Eventually reach me on #gedit
I get identical output to running gedit without the --debug option. However, I found out this morning that by booting into gnome as root and running gedit that gedit runs perfectly. As such, I'd say that something is screwed up in my system permissions. I apologise for not trying this earlier, does anyone know what could be causing this? I installed garnome into an /opt/garnome folder and haven't touched the permissions since then. All other apps work fine. I haven't touched the priority or severity settings of this bug, but I guess you'll probably want to lower it. Boy am I red-faced. :(
Do you still have this problem?
Mark: ?
My apologies for the delay in getting back to you, I've been without an internet connection for quite some time. I no longer have this problem, but that's due to my having a new PC with Slackware 9.1 on. I never did manage to find out exactly what was causing this issue on my old LFS system, but it must have been fairly specific to my system or you'd have been inundated with people reporting this by now. Thanks for your time, Mark