Red Hat Bugzilla – Bug 14288
gdict not starting (or starting too much ...)
Last modified: 2008-05-01 11:37:56 EDT
When starting gdict under KDE, I do get the message that the panel has crashed. (Well, it should actually say that it needs the GNOME panel (does it?) ...) When logging in via telnet and starting gdict, the whole GNOME panel is started! (On the remote machine there's a KDE desktop running - RHAT 6.1. This shouldn't matter - should be the same for a GNOME desktop).
gdict has a --noapplet option that may work around this, if that's useful for you. Can you clarify the bug though: - what is the _exact_ error message when the panel doesn't start? I need to use grep to find it, because I can't find the relevant code - if the panel starts up, is it starting up on the beta3 machine or the 6.1 machine, and which machine is the telnet client?
Thanks, --noapplet works. The exact error messages. (gnome window:) Application "panel" (process 3289) has crashed due to a fatal error. (Segmentation fault) (gnome window:) Application "gdict" (process 3282) has crashed due to a fatal error. (Segmentation fault) (command line:) ** WARNING **: file applet-widget.c: line 934: Corba Exception: type = 2 exid = IDL:CORBA/COMM_FAILURE:1.0 ** WARNING **: Cannot start CORBA
Forgot to answer your second question: the remote machine (ie. the one from which I am doing the telnet to the beta 3 machine) is Red Hat Linux 6.1. The panel is started on the beta 3 machine and displayed on my Red Hat 6.1 computer.
Since: 1. gdict works under GNOME 2. gdict --noapplet works anywhere 3. The remote behaviour without --noapplet is expected (it would start a panel in order to be an applet inside the panel). I think it is best to declare this NOTABUG.