Bug 67812
Summary: | dateconfig crashes when used over ssh | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Need Real Name <dimitrisantana> |
Component: | up2date | Assignee: | Adrian Likins <alikins> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | |
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: | 2004-04-05 20:54:53 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
Need Real Name
2002-07-02 11:56:22 UTC
Can you run any GUI app over the network connection? I just tried that and I realized I wasn't able to. When I had trouble running up2date, I was doing it as "up2date -uv --nox". I just tried running it to call forth the GUI, and I got the error message "No interactive mode available". I can't seem to run any GUI app as root. I even tried it with netscape and it gave me the error message "Error: Can't open display: b006:0.0". I made sure I had exported it as per RedHat support (export DISPLAY=b006:0.0) before I ran it. I then tried running it as uid "dimitri" and I got mixed results. I tried running netscape and it worked. I tried dateconfig as uid dimitri and a pop up box requested the root password. When I gave it, the program crashed. It seems that anything "root" related that has to do with a GUI will not run. Hope this helps. Ok, that's what I thought. Something has messed up the way that the operating system forwards the display, and this is keeping dateconfig from starting. in other words, dateconfig is affected by the problem, but dateconfig is not the problem itself. Since you say that things went wrong after running up2date, I'm going to change the component of this bug report to up2date. It is unlikely that up2date itself is the problem. More likely, one of the packages that up2date installed caused the error, but the up2date developers will be more likely to be able to track down the problem than I can. What is the status of this issue? Were you able to reproduce the problem on your end? unable to reproduce, need more info Not aware of any problems with this with currently supported releases (And not sure this was an up2date issue to begin with). So closing "currentrelease" |