← Back to team overview

kernel-packages team mailing list archive

[Bug 1452318] Re: Faulty behavior when resuming from suspend


On the plus side, 3.19.0-30 fixed this issue. On the minus side, I can't
enter my LUKS passphrase either unless I edit grub options at boot, and
my system actually failed to suspend twice. The second time it did that,
it ran down the battery in my bag.

You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.

  Faulty behavior when resuming from suspend

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  Waking from suspend, everything seems normal, except the graphical
  elements and text on my desktop are not drawn properly. Sometimes,
  moving the mouse over icons can cause them to be redrawn, sometimes
  not. It appears not to matter how I initiate the suspend (e.g. by
  closing laptop lid, or by calling pm-suspend explicitly) and it
  appears not to matter whether I am using an external display or the
  laptop's own screen.

  All other hardware appears to be working, and I can restart the laptop
  by clicking where the icons ought to be. The only symptom seems to be
  that the drawing does not happen correctly.

  I'm not sure what additional information I should provide to help
  diagnose the problem, so please advise me.

  Also, if this is more likely to be a xfce issue, then please change
  the package on the bug report.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: pm-utils 1.4.1-15
  ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3
  Uname: Linux 3.19.0-16-generic x86_64
  NonfreeKernelModules: openafs
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Wed May  6 17:17:51 2015
  InstallationDate: Installed on 2015-05-04 (1 days ago)
  InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1)
  PackageArchitecture: all
  SourcePackage: pm-utils
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to: