Resuming from sleep causes the display number overlay to be shown

Bug #763752 reported by Dylan Damian
22
This bug affects 5 people
Affects Status Importance Assigned to Milestone
fglrx-installer (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

Every time the computer resumes from sleep, the display number overlay (red square with white number) is shown superimposed on the desktop. The only way to make it disappear is to launch ATI Catalyst Control Center from System Settings, select Display Manager from the navigation tree and then toggle the Identify Displays button.

ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: fglrx-amdcccle 2:8.840-0ubuntu2
ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
Uname: Linux 2.6.38-8-generic i686
NonfreeKernelModules: fglrx
Architecture: i386
CompizPlugins: [core,bailer,detection,composite,opengl,decor,mousepoll,vpswitch,regex,animation,snap,expo,move,compiztoolbox,place,grid,imgpng,gnomecompat,wall,ezoom,workarounds,staticswitcher,resize,fade,unitymtgrabhandles,scale,session,unityshell]
CompositorRunning: compiz
Date: Sun Apr 17 12:33:10 2011
DistUpgraded: Fresh install
DistroCodename: natty
DistroVariant: ubuntu
DkmsStatus: fglrx, 8.840, 2.6.38-8-generic, i686: installed
GraphicsCard:
 ATI Technologies Inc RV630 [Radeon HD 2600XT] [1002:9588] (prog-if 00 [VGA controller])
   Subsystem: Info-Tek Corp. Device [18bc:3530]
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Beta i386 (20110413)
JockeyStatus: xorg:fglrx - ATI/AMD proprietary FGLRX graphics driver (Proprietary, Enabled, In use)
MachineType: System manufacturer P5K-E
ProcEnviron:
 LANGUAGE=en_CA:en
 LANG=en_CA.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-2.6.38-8-generic root=UUID=65e5aec6-d383-4e76-9d5e-e28130d4a2c0 ro quiet splash vt.handoff=7
Renderer: Unknown
SourcePackage: fglrx-installer
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/19/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1305
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: P5K-E
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1305:bd06/19/2009:svnSystemmanufacturer:pnP5K-E:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5K-E:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: P5K-E
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
version.compiz: compiz 1:0.9.4+bzr20110411-0ubuntu1
version.fglrx-installer: fglrx-installer N/A
version.libdrm2: libdrm2 2.4.23-1ubuntu6
version.libgl1-mesa-dri: libgl1-mesa-dri 7.10.2-0ubuntu1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 7.10.2-0ubuntu1
version.xserver-xorg: xserver-xorg 1:7.6+4ubuntu3
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.0-0ubuntu4
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.14.0-4ubuntu7
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20110107+b795ca6e-0ubuntu7

Revision history for this message
Dylan Damian (dylan-damian) wrote :
Revision history for this message
Erlend S. Westgaard (erlendsw) wrote :

I worked around this by changing Virtual to my screen resolution (Section "Screen" SubSection "Display" in xorg.conf). Probably not an optimal fix if you use extended desktop.

Revision history for this message
MyMindsAvatar (richjones82) wrote :

I also have this problem, but I'm afraid I'm too new to GNU/Linux to know how to make this change. This is my xorg.conf looks like this below. What should I change?

Section "ServerLayout"
 Identifier "amdcccle Layout"
 Screen 0 "amdcccle-Screen[1]-0" 0 0
EndSection

Section "Module"
 Load "glx"
EndSection

Section "Monitor"
 Identifier "0-LVDS"
 Option "VendorName" "ATI Proprietary Driver"
 Option "ModelName" "Generic Autodetecting Monitor"
 Option "DPMS" "true"
 Option "PreferredMode" "1366x768"
 Option "TargetRefresh" "60"
 Option "Position" "0 0"
 Option "Rotate" "normal"
 Option "Disable" "false"
EndSection

Section "Device"
 Identifier "amdcccle-Device[1]-0"
 Driver "fglrx"
 Option "Monitor-LVDS" "0-LVDS"
 BusID "PCI:1:0:0"
EndSection

Section "Screen"
 Identifier "Default Screen"
 DefaultDepth 24
EndSection

Section "Screen"
 Identifier "amdcccle-Screen[1]-0"
 Device "amdcccle-Device[1]-0"
 DefaultDepth 24
 SubSection "Display"
  Viewport 0 0
  Depth 24
 EndSubSection
EndSection

Revision history for this message
Bryce Harrington (bryce) wrote :

Hey dylan-damian,

You filed this bug report against natty, but I see it's still open and
doesn't appear to have much activity recently. So, now that oneiric
is released and stable, this may be a good point for you to upgrade
and re-test if this issue is still present there.

If it's solved in the new release and you think it's worth backporting
the fix, please indicate that. Or if having the fix in the new release
is good enough, feel free to close out the bug (or let us know and we'll
close it.)

If it's not solved, leave the bug report open. I can't promise we'll
get to it (we get way more bugs filed than we can usually get to), but
your testing and feedback can help out if and when we do.

Changed in fglrx-installer (Ubuntu):
status: New → Incomplete
Revision history for this message
bugbot (bugbot) wrote :

We're closing this bug since it is has been some time with no response from the original reporter. However, if the issue still exists please feel free to reopen with the requested information. Also, if you could, please test against the latest development version of Ubuntu, since this confirms the bug is one we may be able to pass upstream for help.

Changed in fglrx-installer (Ubuntu):
status: Incomplete → Expired
Revision history for this message
Dylan Damian (dylan-damian) wrote :

I can confirm this is no longer happening on oneiric. The bug report can stay closed. Sorry it took me so long to be able to load oneiric on the machine with the original problem.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.