Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 89490 - gnome-print-man generates CORBA errors when starting
Summary: gnome-print-man generates CORBA errors when starting
Keywords:
Status: CLOSED CANTFIX
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: ORBit2
Version: 9
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Matthias Clasen
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: CambridgeTarget
TreeView+ depends on / blocked
 
Reported: 2003-04-23 14:27 UTC by Chris Ricker
Modified: 2007-04-18 16:53 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2007-01-02 19:13:21 UTC
Embargoed:

Attachments (Terms of Use)
patch (deleted)
2004-03-19 19:48 UTC, Mark McLoughlin 		no flags Details | Diff
View All

Description Chris Ricker 2003-04-23 14:27:01 UTC 
When starting gnome-print-man under KDE, I get a dialog box reporting that:

An error occurred while loading or saving configuration information for GNOME
Print Manager. Some of your configuration settings may not work properly.

And then displaying the following errors:



Adding client to server's list failed, CORBA error:
IDL:omg.org/CORBA/COMM_FAILURE:1.0
Adding client to server's list failed, CORBA error:
IDL:omg.org/CORBA/COMM_FAILURE:1.0
Adding client to server's list failed, CORBA error:
IDL:omg.org/CORBA/COMM_FAILURE:1.0
Adding client to server's list failed, CORBA error:
IDL:omg.org/CORBA/COMM_FAILURE:1.0
Adding client to server's list failed, CORBA error:
IDL:omg.org/CORBA/COMM_FAILURE:1.0
Adding client to server's list failed, CORBA error:
IDL:omg.org/CORBA/COMM_FAILURE:1.0
Adding client to server's list failed, CORBA error:
IDL:omg.org/CORBA/COMM_FAILURE:1.0
Adding client to server's list failed, CORBA error:
IDL:omg.org/CORBA/COMM_FAILURE:1.0
Adding client to server's list failed, CORBA error:
IDL:omg.org/CORBA/COMM_FAILURE:1.0
Adding client to server's list failed, CORBA error:
IDL:omg.org/CORBA/COMM_FAILURE:1.0
Adding client to server's list failed, CORBA error:
IDL:omg.org/CORBA/COMM_FAILURE:1.0
Adding client to server's list failed, CORBA error:
IDL:omg.org/CORBA/COMM_FAILURE:1.0
Adding client to server's list failed, CORBA error:
IDL:omg.org/CORBA/COMM_FAILURE:1.0


This isn't a universal KDE problem -- on other machines, gnome-print-man starts
fine under KDE
Comment 1 Tim Waugh 2003-05-06 14:37:02 UTC 
Seems like an ORBit problem.
Comment 2 Need Real Name 2003-06-10 19:26:57 UTC 
sometimes start the gconfd-1, not the gconfd-2. GNOME 2 applications doesn't run
with gconfd-1. The CORBA error is the result of this.
Comment 3 Havoc Pennington 2003-06-11 04:57:08 UTC 
It is a regression in ORBit if gnome 2 apps can't talk to gconfd-1 probably, but 
that still leaves us wondering why gconfd-1 gets started - hmm.

Output of "rpm -q GConf" and "rpm -q GConf2"?

gconfd-1 should have no way to start, because GConf 1 library is hacked to start
gconfd-2 instead. At least, it's supposed to be...
Comment 4 Chris Ricker 2003-06-11 12:04:14 UTC 
[cricker@winsucks cricker]$ rpm -q GConf GConf2
GConf-1.0.9-10
GConf2-2.2.0-1
[cricker@winsucks cricker]$
Comment 5 Mark McLoughlin 2004-03-19 19:46:56 UTC 
Hmm, I backported a GConf1 patch to correctly launch gconfd-2 instead
of gconfd-1.

However, with that patch a GConf1 client which starts the gconfd-2
server fails to contact it. Need to debug that further.
Comment 6 Mark McLoughlin 2004-03-19 19:48:14 UTC 
Created attachment 98691 [details]
patch
Comment 7 Bill Nottingham 2006-08-05 05:13:44 UTC 
Red Hat apologizes that these issues have not been resolved yet. We do want to
make sure that no important bugs slip through the cracks.

Red Hat Linux 7.3 and Red Hat Linux 9 are no longer supported by Red Hat, Inc.
They are maintained by the Fedora Legacy project (http://www.fedoralegacy.org/)
for security updates only. If this is a security issue, please reassign to the
'Fedora Legacy' product in bugzilla. Please note that Legacy security update
support for these products will stop on December 31st, 2006.

If this is not a security issue, please check if this issue is still present
in a current Fedora Core release. If so, please change the product and version
to match, and check the box indicating that the requested information has been
provided.

If you are currently still running Red Hat Linux 7.3 or 9, please note that
Fedora Legacy security update support for these products will stop on December
31st, 2006. You are strongly advised to upgrade to a current Fedora Core release
or Red Hat Enterprise Linux or comparable. Some information on which option may
be right for you is available at http://www.redhat.com/rhel/migrate/redhatlinux/.

Any bug still open against Red Hat Linux 7.3 or 9 at the end of 2006 will be
closed 'CANTFIX'. Again, if this bug still exists in a current release, or is a
security issue, please change the product as necessary. We thank you for your
help, and apologize again that we haven't handled these issues to this point.
Comment 9 Bill Nottingham 2007-01-02 19:13:21 UTC 
Red Hat Linux 7.3 and Red Hat Linux 9 are no longer supported by Red Hat, Inc.
f you are currently still running Red Hat Linux 7.3 or 9, you are strongly
advised to upgrade to a current Fedora Core release or Red Hat Enterprise Linux
or comparable. Some information on which option may be right for you is
available at http://www.redhat.com/rhel/migrate/redhatlinux/.

Closing as CANTFIX.
Note You need to log in before you can comment on or make changes to this bug.