Bug 58714
Summary: | KDE wipes out custom X resource settings. | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Terry Griffin <griffint> |
Component: | kdebase | Assignee: | Petr Rockai <prockai> |
Status: | CLOSED CANTFIX | QA Contact: | Ben Levenson <benl> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 7.2 | ||
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: | 2006-10-18 18:02:56 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
Terry Griffin
2002-01-23 17:57:14 UTC
I have more data: For the scenario where resources are reset after a few minutes, it only seems to happen when (A) I log in remotely via XDMCP (in my case from Reflection X running on NT4), and (B) when the login screen is managed by KDM. In other words, if I log in locally, there's no reset after a few minutes. If I use XDM instead of KDM there's no reset after a few minutes. I've not tried GDM. Even without the two-minute issue, there's still the problem of getting the custom resources set up initially. Putting the xrdb command in Autostart seems to work most of the time, but from time to time it doesn't take. This is independent of local or remote login and KDM vs. XDM. This bug is reported against old release of Red Hat Linux or Fedora Core that is no longer supported. Chances are that it has been already fixed in newer Fedora Core release. If you still experience the problem with current release of Fedora Core, please update the Version field (you may need to switch Product to Fedora Core first) in the bug report and put it back to NEW state. Red Hat Linux is no longer supported by Red Hat, Inc. If you are still running Red Hat Linux, 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/. 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. If this issue is still present in a current Fedora Core release, please open a new bug with the relevant information. Closing as CANTFIX. |