Bug 202333
Summary: | Kyum reports network address errors from _ICE | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | G.Wolfe Woodbury <redwolfe> |
Component: | kyum | Assignee: | Jochen Schmitt <jochen> |
Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | low | Docs Contact: | |
Priority: | medium | ||
Version: | 5 | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2007-04-24 09:09:42 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: |
Description
G.Wolfe Woodbury
2006-08-12 23:51:15 UTC
Thank you for reporting your problem. Unfortunately I was unable to reproduced your problem. so I need some additional information about your environment. Best Regards: Jochen Schmitt The system in question is a fully up-to-date FC5 installation.
the lines in question are:
>_IceTransOpen: Unable to Parse address
>Session management error: Could not open network socket
>_IceTransOpen: Unable to Parse address
>Session management error: Could not open network socket
>kbuildsycoca running...
>_IceTransOpen: Unable to Parse address
>Session management error: Could not open network socket
CPU: Intel Celeron @ 1.8GHz 1.5GB RAM SiS Chipset
IDE drives: 1TB online SiS900 NIC etc.
Not running Xen.
Have to start kyum from the command line to see the above errors.
What other information do you need?
I actually see this error from several other KDE applications under FC6 and FC7 when started from the command line. I suspect that there was some sort of change in the API (most likely involving a pointer vs. something else) for the ICE library. dropping bug report as it seems to be a general KDE interface bug and not KYum's problem. |