Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • xorgproto xorgproto
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 14
    • Issues 14
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 6
    • Merge requests 6
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • xorg
  • proto
  • xorgprotoxorgproto
  • Issues
  • #2

Closed (moved)
(moved)
Open
Created Aug 06, 2008 by Bugzilla Migration User@bugzilla-migration

Xinerama + XCopyArea/Xdamage

Submitted by Anton Fedorov

Assigned to Aaron Plattner @aplattner

Link to original bug (#17013)

Description

XCopyArea copies blank from second monitor. Also, seems that Xdamage doesn't produce messages for changes on second monitor.

As result, correctly working in single-screen setups applications fail to work on xinerama setups.

F.e., vino ( http://bugzilla.gnome.org/show_bug.cgi?id=346258 ) shows completely blank second screen, and if disable XCoypArea, it shows no changes on second screen (seems, with no Xdamage information on it).

Version: 7.3 (2007.09)

Blocking

  • Bug 44202
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking