Summary: | XineramaIsActive disagrees with XineramaQueryScreens | ||
---|---|---|---|
Product: | xorg | Reporter: | Brice Goglin <brice.goglin> |
Component: | Server/General | Assignee: | Keith Packard <keithp> |
Status: | RESOLVED FIXED | QA Contact: | Xorg Project Team <xorg-team> |
Severity: | normal | ||
Priority: | medium | CC: | ema |
Version: | 7.2 (2007.02) | ||
Hardware: | Other | ||
OS: | All | ||
URL: | http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=432256 | ||
Whiteboard: | |||
i915 platform: | i915 features: | ||
Bug Depends on: | |||
Bug Blocks: | 8888 |
Description
Brice Goglin
2007-07-09 01:09:15 UTC
Drivers with functions like RADEONProcXineramaDispatch are providing their own functions for reporting Xinerama info when using things like MergedFB and TwinView that Xinerama-like but not using the X server's Xinerama implementation. Drivers shouldn't need functions like this if they can only ever output to a single display at once, but can be combined with other devices into a multihead configuration using the Xserver's Xinerama implementation. (In other words, while you seem to have found a bug, I believe the "wild guess" is looking in the wrong direction.) It does not look sparc-specific after all, according to Joe Pfeiffer in the same Debian bug, it occurs on i386 with the vesa driver too. From his /var/log/syslog: Jul 25 23:36:12 Valiant gdm[3392]: Xinerama active, but <= 0 screens? Jul 25 23:36:32 Valiant gdm[3384]: gdm_child_action: Aborting display :0 This bug might be related to this one https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=234567 which ajax fixed with http://cvs.fedora.redhat.com/viewcvs/rpms/xorg-x11-server/devel/xserver-1.3.0-randrama-no-zero-screens.patch?rev=1.1&view=auto But I don't think this patch has been pushed upstream yet. Debian submitter confirms the above patch solves the problem. I am marking this bug as a blocker for 7.3 then. Keith said that the ajax fix was on the right track but not quite correct, and expressed interest in fixing it. (In reply to comment #5) > Keith said that the ajax fix was on the right track but not quite correct, and > expressed interest in fixing it. It certainly seems to work for me. What's wrong with it? cherry-picked to server-1.4-branch |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.