← Back to team overview

ubuntu-x-swat team mailing list archive

[Bug 528138] Re: garbage on screen after suspend

 

** Description changed:

  Binary package hint: xorg
  
  Hello!
  
  I've just updated to Lucid*; the most visible change is that suspend
  stopped working correctly. Actually, suspend works, but resuming seems
  to have a problem. First, when resuming the screen doesn't turn on
- immediately; I lost patience every time and switched terminals (blindly)
- a few times as well as pressed a few keys; eventually the screensaver's
- password dialog came up, but I'm not sure if it was just a delay or if
- my key-presses turned it back on.
+ immediately; pressing the num-lock key the LED on the keyboard changes,
+ however the monitor claims it doesn't receive any signal. I tried
+ various tinkering with the keys. If I press Ctrl-Alt-F1 through to Ctrl-
+ Alt-F7 the screen turns on and the screensaver's password dialog came
+ up. That one works all the time; I tried shorter sequences, like just
+ C-A-F1 then C-A-F7 and that didn't work. I've no idea what's going on.
  
  Anyway, that's not what I'm reporting: the main problem is that after I
  enter the password and return to my desktop some pixmaps seem to have
  been replaced by garbage. I'll attach a couple of screenshots that show
  this better than I can describe it.
  
  (*: note that this is a machine that has been dist-upgraded from at
  least Edgy, so it might be a bit different from a new install. I don't
  have access to a CD writer, so I can't test the live CD.)
  
  In the  first screenshot this is mostly visible in the desktop image. I
  killed Nautilus and when it restarted the garbage was replaced by the
  correct image. However, as can be seen in the second image, corruption
  remains in programs that haven't yet been restarted (window shadows and
  icons are the most obvious).
  
  I've assigned this provisionally to xorg, but I've no idea if it's
  responsible. Note that as far as I can tell everything works pretty much
  correctly (other than the obvious), in the sense that programs work and
  I've not noticed crashes or the like even after a long time in this
  “garbage” state. Everything goes back to correctness if I log out and
  then back in.
  
  ProblemType: Bug
  Architecture: amd64
  Date: Fri Feb 26 01:12:25 2010
  DistroRelease: Ubuntu 10.04
  DkmsStatus: nvidia-current, 195.36.03, 2.6.32-14-generic, x86_64: installed
  EcryptfsInUse: Yes
  MachineType: System manufacturer P5Q-PRO
  NonfreeKernelModules: nvidia
  Package: xorg 1:7.5+1ubuntu8
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-14-generic root=/dev/sda1 ro vga=892
  ProcEnviron:
-  LANGUAGE=en_US.UTF-8
-  PATH=(custom, user)
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
+  LANGUAGE=en_US.UTF-8
+  PATH=(custom, user)
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.32-14.20-generic
  RelatedPackageVersions:
-  xserver-xorg 1:7.5+1ubuntu8
-  libgl1-mesa-glx 7.7-3ubuntu1
-  libdrm2 2.4.18-1ubuntu2
-  xserver-xorg-video-intel N/A
+  xserver-xorg 1:7.5+1ubuntu8
+  libgl1-mesa-glx 7.7-3ubuntu1
+  libdrm2 2.4.18-1ubuntu2
+  xserver-xorg-video-intel N/A
  SourcePackage: xorg
  Uname: Linux 2.6.32-14-generic x86_64
  dmi.bios.date: 11/04/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1501
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5Q-PRO
  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.:bvr1501:bd11/04/2008:svnSystemmanufacturer:pnP5Q-PRO:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5Q-PRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: P5Q-PRO
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  system:
-  distro:             Ubuntu
-  architecture:       x86_64kernel:             2.6.32-14-generic
+  distro:             Ubuntu
+  architecture:       x86_64kernel:             2.6.32-14-generic

** Description changed:

  Binary package hint: xorg
  
  Hello!
  
  I've just updated to Lucid*; the most visible change is that suspend
  stopped working correctly. Actually, suspend works, but resuming seems
  to have a problem. First, when resuming the screen doesn't turn on
  immediately; pressing the num-lock key the LED on the keyboard changes,
  however the monitor claims it doesn't receive any signal. I tried
  various tinkering with the keys. If I press Ctrl-Alt-F1 through to Ctrl-
  Alt-F7 the screen turns on and the screensaver's password dialog came
  up. That one works all the time; I tried shorter sequences, like just
  C-A-F1 then C-A-F7 and that didn't work. I've no idea what's going on.
  
- Anyway, that's not what I'm reporting: the main problem is that after I
- enter the password and return to my desktop some pixmaps seem to have
- been replaced by garbage. I'll attach a couple of screenshots that show
- this better than I can describe it.
+ Anyway, the main problem is that after I enter the password and return
+ to my desktop some pixmaps seem to have been replaced by garbage. I'll
+ attach a couple of screenshots that show this better than I can describe
+ it. (I'm not sure if I should split the two problems in two bug reports;
+ for all I know they might be related.)
  
  (*: note that this is a machine that has been dist-upgraded from at
  least Edgy, so it might be a bit different from a new install. I don't
  have access to a CD writer, so I can't test the live CD.)
  
  In the  first screenshot this is mostly visible in the desktop image. I
  killed Nautilus and when it restarted the garbage was replaced by the
  correct image. However, as can be seen in the second image, corruption
  remains in programs that haven't yet been restarted (window shadows and
  icons are the most obvious).
  
  I've assigned this provisionally to xorg, but I've no idea if it's
  responsible. Note that as far as I can tell everything works pretty much
  correctly (other than the obvious), in the sense that programs work and
  I've not noticed crashes or the like even after a long time in this
  “garbage” state. Everything goes back to correctness if I log out and
  then back in.
  
  ProblemType: Bug
  Architecture: amd64
  Date: Fri Feb 26 01:12:25 2010
  DistroRelease: Ubuntu 10.04
  DkmsStatus: nvidia-current, 195.36.03, 2.6.32-14-generic, x86_64: installed
  EcryptfsInUse: Yes
  MachineType: System manufacturer P5Q-PRO
  NonfreeKernelModules: nvidia
  Package: xorg 1:7.5+1ubuntu8
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-14-generic root=/dev/sda1 ro vga=892
  ProcEnviron:
   LANGUAGE=en_US.UTF-8
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.32-14.20-generic
  RelatedPackageVersions:
   xserver-xorg 1:7.5+1ubuntu8
   libgl1-mesa-glx 7.7-3ubuntu1
   libdrm2 2.4.18-1ubuntu2
   xserver-xorg-video-intel N/A
  SourcePackage: xorg
  Uname: Linux 2.6.32-14-generic x86_64
  dmi.bios.date: 11/04/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1501
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5Q-PRO
  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.:bvr1501:bd11/04/2008:svnSystemmanufacturer:pnP5Q-PRO:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5Q-PRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: P5Q-PRO
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  system:
   distro:             Ubuntu
   architecture:       x86_64kernel:             2.6.32-14-generic

-- 
garbage on screen after suspend
https://bugs.launchpad.net/bugs/528138
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in ubuntu.



References