Bug 3440 - [BROKEN BUG] xf86RandRSetMode() calling EnableDisableFBAccess before return
Summary: [BROKEN BUG] xf86RandRSetMode() calling EnableDisableFBAccess before return
Status: RESOLVED DUPLICATE of bug 4635
Alias: None
Product: xorg
Classification: Unclassified
Component: Server/General (show other bugs)
Version: 6.8.2
Hardware: x86 (IA32) Linux (All)
: high normal
Assignee: Xorg Project Team
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 1690
  Show dependency tree / graph
 
Reported: 2005-05-31 11:03 UTC by Daniel Stone
Modified: 2005-09-30 07:10 UTC (History)
0 users

See Also:
i915 platform:
i915 features:

Attachments

Description FreeDesktop Bugzilla Database Corruption Fix User 2005-05-31 11:03:43 UTC 
File: /xc/programs/Xserver/hw/xfree86/common/xf86RandR.c
Function: xf86RandRSetMode()

If xf86SwitchMode() returns false and pRoot is true, the function returns
without enabling FBAccess, causing X server to stall.
Comment 1 Daniel Stone 2005-08-28 05:57:01 UTC 
argh, broken bug.
Comment 2 Alan Coopersmith 2005-10-01 00:04:20 UTC 
xorg-team archives say the original content was:

           Summary: xf86RandRSetMode() calling EnableDisableFBAccess before
                    return
           Product: xorg
           Version: 6.8.2
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Server/general
        AssignedTo: xorg-team at lists.x.org
        ReportedBy: jason.you at 3dlabs.com


File: /xc/programs/Xserver/hw/xfree86/common/xf86RandR.c
Function: xf86RandRSetMode()

If xf86SwitchMode() returns false and pRoot is true, the function returns
without enabling FBAccess, causing X server to stall.
Comment 3 Alan Coopersmith 2005-10-01 00:10:40 UTC 
Sounds like a dup of problem #1 in bug 4635 to me, closing as dup.

*** This bug has been marked as a duplicate of 4635 ***

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.