@Khurshid: In which case it's a different bug which should be reported
as a new one separately. This one is about AMD/ATI cards/drivers, not
Intel.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to fglrx-installer in Ubuntu.
This bug has returned for me on Xenial for Intel 965 GMA and many other
older intel video drivers.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to fglrx-installer in Ubuntu.
https://bugs.launchpad.net/bugs/969860
Title:
fglrx uses
... unfortunately I realized that my problem begins NOT with screensaver
activation, but screen LOCK activation.
During test I switched off the LOCK, this is why my problem seemed to be solved.
I found another bug report which describes my problem:
I faced with exactly the same problem with different hardware:
Data:
- Fresh install of Ubuntu 15.10 (plus some other non-desktop or gnome related
packages)
- All energy consumption related settings are default (I have not changed them
till now).
- Laptop: ACER Aspire V3-371-51
- CPU: Intel
I am using Dell latitude e7440, Ubuntu trusty, having the same problem.
Every time I lock my screen using -L, after a few seconds my
vent goes crazy and the temperature rises to 80+ Celsius.
I could not run the `dstack` file properly. The output of `sh ./dstack compiz >
compizstack.txt` was
I've just upgraded to the Catalyst 13.11 Beta Drivers linked in #104 and
my CPU utilization issue has gone away. When the monitor shuts off, the
CPU usage goes down instead of to 100%
I'm going to say fixed for me with latest 13.11 drivers
--
You received this bug notification because you are
OK then. I haven't retested myself but trust both comment #105 and the
upstream bug info. Therefore fix released somewhere around:
fglrx-installer (2:13.101-0ubuntu1) saucy; urgency=low
fglrx-installer-updates (2:13.101-0ubuntu1) saucy; urgency=low
** Changed in: fglrx-installer (Ubuntu)
** Tags added: battery-power-consumption quantal
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to fglrx-installer in Ubuntu.
https://bugs.launchpad.net/bugs/969860
Title:
fglrx uses 100% CPU when screen turns off (spinning in
Just to check, Can anyone confirm that this is still a problem with the
Catalyst 13.11 Beta drivers?
http://support.amd.com/en-us/kb-articles/Pages/Latest-LINUX-Beta-
Driver.aspx
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
Either the upstream bug was re-introduced or never really fixed because
I'm running the amd-catalyst-13.8 beta2 version (fglrx 13.2000). As
soon as the screen shuts off, the CPU usages spikes to 100%. Neither of
the workarounds work for me. I've been forced to just turn off X at
night.
I've
No issues with amd-catalyst-13.8 beta2 (since 12.12 for that matter) in
combination with GNOME Shell (3.8) on Ubuntu GNOME 13.04 for me.
@David: Are you using Unity or GNOME Shell and which version of Ubuntu
are you running?
--
You received this bug notification because you are a member of
I'm running Ubuntu 12.10 quantal with the amd-catalyst-13.8 beta2
drivers downloaded from the AMD website and compiled/installed on the
system. I've not tried GNOME but I've seen this in the other xsession
environments. The primary use of this box is running a standalone xbmc
instance though.
WORKAROUND (2):
1. Run ccsm (from package compizconfig-settings-manager)
2. In OpenGL Sync To VBlank = OFF
worked for me in Ubuntu 12.04
Thanks
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to fglrx-installer in Ubuntu.
Patrick, is this the bug you are experiencing?:
http://ati.cchtml.com/show_bug.cgi?id=553
This is what I'm currently experiencing using KDE + fglrx drivers,
unless I use the xrender backend or disable compositing altogether.
Unfortunately, using xrender causes issues with windowed OpenGL apps not
I'm running Kubuntu 12.10 and this bug continues to affect me with 13.1,
using .deb packages I built automatically from their 13.1 installer.
It looks like this is just as ‘fixed’ as their ‘Konsole resize causes X
crash’ bug.
--
You received this bug notification because you are a member of
Patrick, does using Xrender as kwin's compositing backend work as a
workaround? That's how I resolved my blank screen freezes using previous
versions of the fglrx driver. I haven't been able to get a freeze using
13.1 + kwin OpenGL backend yet, but we'll see...
--
You received this bug
Bug affects me as well.
** Changed in: compiz (Ubuntu)
Status: Invalid = Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to fglrx-installer in Ubuntu.
https://bugs.launchpad.net/bugs/969860
Title:
fglrx uses 100% CPU
This is an upstream bug, and it's been fixed in 13.1 so please either
install 13.1 or wait until Ubuntu updates fglrx in the repository (even
though they are practically the same -- minus a few differences -- if
you build them.)
** Changed in: compiz (Ubuntu)
Status: Confirmed = Invalid
blablack: I'm not aware of AMD sharing their release schedule with us.
When it is available from AMD, you should keep an eye on:
https://launchpad.net/ubuntu/+source/fglrx-installer
https://launchpad.net/ubuntu/+source/fglrx-installer-updates
Our package maintainer might have more info:
Alberto
Quick questions - Once the driver is released by AMD:
- Will it be available in Ubuntu 12.10?
- Which version of the driver will be updated: fglrx or fglrx-updates?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to fglrx-installer in
@Daniel: That does not explain why Gnome Shell users had the same issue
earlier. For the record, I have vsync enabled in CCC and no high CPU
issue to be seen.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to fglrx-installer in Ubuntu.
Regardless of what is affected and what is not... AMD have confirmed
their driver is to blame and they have a fix.
If Gnome is not affected, that's awesome. But we don't need to worry
about why.
--
You received this bug notification because you are a member of Desktop
Packages, which is
I can confirm Forage's comment: Ubuntu 12.10 Gnome Remix does not have this
problem.
I switched from Ubuntu 12.10 to the Gnome Remix and the problem seemed to solve
itself. And I will note that I am running the exact same
drivers/programs/extensions that I was when I was experiencing the
I agree with Kellen Hawley.
Gnome Remix couldn't solve this problem.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to fglrx-installer in Ubuntu.
https://bugs.launchpad.net/bugs/969860
Title:
fglrx uses 100% CPU when screen turns off
Oops.. Sorry, I mean.. disagree.
I experience High CPU usage in Gnome Remix, too
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to fglrx-installer in Ubuntu.
https://bugs.launchpad.net/bugs/969860
Title:
fglrx uses 100% CPU when screen
Gnome probably does not suffer from this bug if it doesn't have any
vsync enabled by default. That's equivalent to WORKAROUND (2) listed
at the top of the bug.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to fglrx-installer in Ubuntu.
I forgot all about that until you had mentioned the 12.12 driver, for
those of you who cannot wait you can get the 12.11 beta (which of course
is the 12.12) and install it:
http://support.amd.com/us/kbarticles/Pages/AMDCatalyst1211betadriver.aspx
--
You received this bug notification because you
And for those who can't wait: Ubuntu 12.10 GNOME remix still works like
a charm. No compiz, no CPU issues, with tear-free enabled.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to fglrx-installer in Ubuntu.
** Changed in: fglrx
Status: Unknown = Confirmed
** Changed in: fglrx
Importance: Unknown = Medium
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to fglrx-installer in Ubuntu.
https://bugs.launchpad.net/bugs/969860
Title:
P.S. Compiz is open source. Canonical is not to blame for things not
getting fixed, but everyone is.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to fglrx-installer in Ubuntu.
https://bugs.launchpad.net/bugs/969860
Title:
fglrx uses
I agree it's critical and I would love to have time to work on it.
Hopefully this week.
Please stop complaining about status changes. So many people complain
about status changes that I mostly don't bother changing bug status's
even when I should, just so no one will complain.
--
You received
I have to agree with Jordan.
This fried one of my laptops and actually made me move to kubuntu.
Sent from my BlackBerry® wireless device
-Original Message-
From: Jordon Bedwell 969...@bugs.launchpad.net
Sender: boun...@canonical.com
Date: Mon, 19 Nov 2012 07:49:53
To:
** Also affects: fglrx via
http://ati.cchtml.com/show_bug.cgi?id=535
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to fglrx-installer in Ubuntu.
https://bugs.launchpad.net/bugs/969860
Crap, I had a strong suspicion this was the case because I too didn't
experience this bug in 12.10 but 12.10 did not really appeal to my
tastes (because of some personal reasons that aren't necessary to this
bug.) I don't remember if I ever mentioned that in another bug or not.
Just as a side
OK, I've spent hours testing various options. The bug is much harder to
reproduce in Ubuntu 12.10 because the default rendering method in Compiz 0.9.8
is the same as the workaround (1) listed at the top of the bug. To reproduce
the bug I had to force the rendering method that Compiz 0.9.7 uses:
With the fglrx driver on my laptop using Kubuntu, I have to turn off
screen blanking, because every once in a while it causes my system to
hang when the screen blanks. I am able to reset gracefully using
ALT+PrintScrn+REISUB. I wonder if this is related to the same fglrx bug.
I will try running my
Jordan: I have already mentioned all the settings I've changed in
comment #80.
However if you want an optimal tear-free experience then you should not
change the compiz settings. The default compiz settings in 12.10 give
the optimal tear-free experience, unless it's disabled in your driver
AMD tell me the fix is complete and will appear in Catalyst 12.12 (which
I think means the December release?).
I'm still confused about the relationship between the Catalyst version
number (year.month?) and the fglrx version number that comes from it.
But AMD also tell me that it will be made
** Changed in: compiz-core
Milestone: 0.9.7.10 = 0.9.7.12
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to fglrx-installer in Ubuntu.
https://bugs.launchpad.net/bugs/969860
Title:
fglrx uses 100% CPU when screen turns off (spinning
Why is this constantly being pushed? And being pushed at all, this is a
pretty critical issue that breaks quite a few laptops, I don't even
understand why you would ignore an issue like this and push it instead
of making it a top priority issue...
--
You received this bug notification because
While we're at it, can anyone update us on the status of this bug in
Precise? When I tested it on Quantal it was working exactly as intended
with no side-affects like this so I'm wondering if there are plans to
fix this soon? Since it seems like it didn't make it into the point.
--
You received
What version is the fixed one?
I have updated my comiz to 0.9.8.4-bzr3407, but the problem still
exists.
What can I do?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to fglrx-installer in Ubuntu.
https://bugs.launchpad.net/bugs/969860
** Changed in: compiz
Status: Triaged = Fix Released
** Changed in: compiz/0.9.8
Status: Triaged = Fix Released
** Changed in: compiz-core
Status: Triaged = Fix Released
** Changed in: ubuntu-power-consumption
Status: Confirmed = Fix Released
** Changed in: compiz
** Changed in: compiz
Status: Fix Released = Triaged
** Changed in: compiz/0.9.8
Status: Fix Released = Triaged
** Changed in: compiz-core
Status: Fix Released = Triaged
** Changed in: compiz (Ubuntu)
Status: Fix Released = Triaged
** Changed in: fglrx-installer
** Also affects: compiz-core
Importance: Undecided
Status: New
** Changed in: compiz-core
Status: New = Triaged
** Changed in: compiz-core
Importance: Undecided = High
** Changed in: compiz-core
Milestone: None = 0.9.7.10
--
You received this bug notification because
I had the same problem using a Ubuntu 12.10/Gnome 3.6/Radeon HD 6650M
/fglrx-updates set up. None of the workarounds worked for gnome-shell
(although they worked when using Unity).
My workaround was to uninstall gnome-screensaver and replace it with
xscreensaver.
--
You received this bug
As of Ubuntu 12.10 GNOME remix in combination with AMD CCC 12.11 beta
(fglrx 9.010) the issue has disappeared! Note that I did a complete
fresh install (not perserving the home folder either) and I have yet to
test it with tear free and vsync on, but so far so good.
--
You received this bug
still affects me on 12.10 Gnome Remix
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to fglrx-installer in Ubuntu.
https://bugs.launchpad.net/bugs/969860
Title:
fglrx uses 100% CPU when screen turns off (spinning in
I had the same problem for a while now, until recently I found a
solution which I'm going to share with you. I know it's not the ideal
approach, but I hope it will be useful for you guys until someone fixes
the issue.
Investigating I found that installing Caffeine in my Ubuntu 12.04.1 and
Is this bug solved in Ubuntu 12.10 ?? I cant't test beta2 by myself
right now, sorry.
@DanielVanVugt, if you need some test, logs or alternative workarounds,
I can help (if you want, of course)
--
You received this bug notification because you are a member of Desktop
Packages, which is
no it was not with beta 1.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to fglrx-installer in Ubuntu.
https://bugs.launchpad.net/bugs/969860
Title:
fglrx uses 100% CPU when screen turns off (spinning in
glXWaitVideoSyncSGI or
** Changed in: compiz
Milestone: 0.9.8.4 = 0.9.9.0
** Changed in: compiz
Assignee: Daniel van Vugt (vanvugt) = (unassigned)
** Also affects: compiz/0.9.8
Importance: Undecided
Status: New
** Changed in: compiz/0.9.8
Status: New = Triaged
** Changed in: compiz/0.9.8
52 matches
Mail list logo
