Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#8429 - fglrx 8.42 distorted watermark on lower right corner the screen

Attached to Project: Arch Linux
Opened by Panos Papadopoulos (disharmonic) - Friday, 26 October 2007, 22:31 GMT
Last edited by Travis Willard (Cerebral) - Friday, 16 November 2007, 15:54 GMT
Task Type Bug Report
Category Packages: Testing
Status Closed
Assigned To Travis Willard (Cerebral)
Architecture i686
Severity Low
Priority Normal
Reported Version 2007.08-2
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
Well the title pretty much sais it all. There is a watermark on th lower right corner of the screen. I first had this with 8.41. i'll add a picture later.
Hardware X2 4600, X1800XT 512MB, 2GB ram, kernel 2.6.23.1(core)

Additional info:
* package version(s)
* config and/or log files etc.


Steps to reproduce:
This task depends upon

Closed by  Travis Willard (Cerebral)
Friday, 16 November 2007, 15:54 GMT
Reason for closing:  Won't fix
Additional comments about closing:  Upstream bug that we can't deal with. For now, add

Option "XAANoOffscreenPixmaps" "true"

to your fglrx device section to clear it up.
Comment by Panos Papadopoulos (disharmonic) - Saturday, 27 October 2007, 11:45 GMT
Ok here's the pic. Any other info on my system required ? xorg.conf etc?
Comment by Travis Willard (Cerebral) - Monday, 29 October 2007, 15:41 GMT
Known problem with fglrx 8.41 and 8.42.

People have reported a 'fix' by adding:
Option "XAANoOffscreenPixmaps" "true"

To their device sections in xorg.conf - maybe it'll work for you too. Other than that, nothing we can do to fix it.
Comment by João Rodrigues (gothicknight) - Thursday, 08 November 2007, 08:35 GMT
I can confirm the bug and the workaround to it. This can be closed IMHO as this is a mainstream bug, not in archlinux package.
A warning could be posted in package install for this though.

Loading...