Bug 140441
| Summary: | Mysterious side-effects cause dual-head to work properly | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Andrew D. Stadler <stadler> |
| Component: | system-config-display | Assignee: | Adam Jackson <ajax> |
| Status: | CLOSED CANTFIX | QA Contact: | |
| Severity: | high | Docs Contact: | |
| Priority: | medium | ||
| Version: | 3 | ||
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | i686 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2006-10-31 15:52:57 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: | 150223 | ||
|
Description
Andrew D. Stadler
2004-11-22 21:48:57 UTC
Can you test with system-config-display from updates testing: system-config-display-1.0.24 Assuming that this is the same as system-config-display-1.0.24-1-noarch.rpm, then yes, all of these tests were already run with this newer system-config-display. (I had already upgraded to it, per your recommendation in bug 140201.) Apologies - I misread. What happens if you disable rhgb- set GRAPHICAL=no in /etc/sysconfig/init I tried the following test: 1. Removed the /etc/rhgb/xorg.conf (to go back to original, troubled configuration) 2. Edited /etc/sysconfig/init and changed GRAPHICAL to =no Result: System booted using text mode only, and eventually switched to graphic login screen, with both monitors operating properly. So it seems that *either* workaround resolves the problem: single-head /etc/rhgb/xorg.conf file, or, GRAPHICAL=no in /etc/sysconfig/init Note, this test helps narrow down the issues in my other bug, # 140435, which was more about the crashing in rhgb. Any ideas about steps 6-7-8 in the original writeup, the core of this bug, about the mysterious ability of s-c-d to fix the system without making any obvious change to /etc/X11/xorg.conf ? I imagine that this is as we are respawning the X server, running system-config-display probably involved you restarting it. A simple test to eliminate system-config-display from the picture - boot into original, troubled config. Ctrl-Alt-Backspace to zap X Does X restart correctly laid out? I wasn't sure at which point you wanted me to zap X, so I tried a few points. At #2 (hung) nothing happened. At #3 (hung) nothing happened Ugh, #4 no longer works. Now, even with the 2nd monitor unplugged, it is dying at "setting the hostname". Apparently the original steps to reproduce are no longer working.... I will need to work out a different set of steps before I can perform your test.... Mass update: move dual head bugs from FC5 to FC6, no way they can get fixed before FC5 release at this point. Closing per lack of response to previous request for information. This bug was originally filed against a much earlier version of Fedora Core, and significant changes have taken place since the last version for which this bug is confirmed. Note that FC3 and FC4 are supported by Fedora Legacy for security fixes only. Please install a still supported version and retest. If it still occurs on FC5 or FC6, please reopen and assign to the correct version. Otherwise, if this a security issue, please change the product to Fedora Legacy. Thanks, and we are sorry that we did not get to this bug earlier. Just a followup, I didn't abandon this bug. I have not been able to follow up because after upgrading to FC5, dual-head became completely unuseable on my system. (Somewhere between FC4 and FC5 the driver for the radeon 7500 became quite flaky in dual-head mode). fedora #185944 fedora #190751 freedesktop #5781 freedesktop #7019 I will be more than happy to regress this bug... if I ever regain dual-head useability.... |