← Back to team overview

kernel-packages team mailing list archive

[Bug 998310] Re: .Xmodmap file makes xorg temporarily reach high cpu usage (90%-100%) after resume or when coming back from tty to X session


peer_gynt, thank you for your comment. Unfortunately, reporting bugs about Mint wouldn't be terribly helpful here. However, if this would be reproducible in Ubuntu with your hardware, please feel free file a new report in Ubuntu (not Mint) by executing the following in a terminal:
ubuntu-bug xorg

Please ensure you have xdiagnose installed, and that you click the Yes
button for attaching additional debugging information.

For more on this, please see the official Ubuntu documentation:
Ubuntu X.Org Team, Ubuntu Bug Control, and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Please note, not filing a new report will delay your problem being
addressed as quickly as possible.

Thank you for your understanding.

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

  .Xmodmap file makes xorg temporarily reach high cpu usage (90%-100%)
  after resume or when coming back from tty to X session

Status in “linux” package in Ubuntu:

Bug description:
  Each time when I resume my laptop, my computer nearly freezes for
  about 5 minutes and Xorg is using 90-100% cpu. This issue disappears
  and then everything is back to normal.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: xorg 1:7.6+12ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-24.38-generic 3.2.16
  Uname: Linux 3.2.0-24-generic x86_64
  ApportVersion: 2.0.1-0ubuntu7
  Architecture: amd64
  Date: Fri May 11 22:57:03 2012
  EcryptfsInUse: Yes
  InstallationMedia: Kubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427)
  SourcePackage: xorg
  UpgradeStatus: Upgraded to precise on 2012-03-25 (47 days ago)

To manage notifications about this bug go to: