Bug 89490
| Summary: | gnome-print-man generates CORBA errors when starting | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Retired] Red Hat Linux | Reporter: | Chris Ricker <chris.ricker> | ||||
| Component: | ORBit2 | Assignee: | Matthias Clasen <mclasen> | ||||
| Status: | CLOSED CANTFIX | QA Contact: | |||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | medium | ||||||
| Version: | 9 | CC: | mattdm, twaugh | ||||
| Target Milestone: | --- | Keywords: | Triaged | ||||
| Target Release: | --- | ||||||
| Hardware: | All | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2007-01-02 19:13:21 UTC | Type: | --- | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Bug Depends On: | |||||||
| Bug Blocks: | 100644 | ||||||
| Attachments: |
|
||||||
|
Description
Chris Ricker
2003-04-23 14:27:01 UTC
Seems like an ORBit problem. 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. 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... [cricker@winsucks cricker]$ rpm -q GConf GConf2 GConf-1.0.9-10 GConf2-2.2.0-1 [cricker@winsucks cricker]$ 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. Created attachment 98691 [details]
patch
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. 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. |