** Changed in: xorg-server
Importance: Unknown = High
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu.
https://bugs.launchpad.net/bugs/307306
Title:
upgrade to 2:1.2.99.2-0ubuntu1 makes session
** Changed in: xorg-server
Importance: High = Unknown
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu.
https://bugs.launchpad.net/bugs/307306
Title:
upgrade to 2:1.2.99.2-0ubuntu1 makes session
** Changed in: gnome-power
Importance: Unknown = Critical
--
upgrade to 2:1.2.99.2-0ubuntu1 makes session utterly slow
https://bugs.launchpad.net/bugs/307306
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-desktop in ubuntu.
--
** Changed in: gnome-desktop
Importance: Unknown = High
--
upgrade to 2:1.2.99.2-0ubuntu1 makes session utterly slow
https://bugs.launchpad.net/bugs/307306
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-desktop in ubuntu.
--
unsubscribe
On Wed, Sep 15, 2010 at 4:43 PM, Bug Watch Updater
307...@bugs.launchpad.net wrote:
** Changed in: gnome-desktop
Importance: Unknown = High
--
upgrade to 2:1.2.99.2-0ubuntu1 makes session utterly slow
https://bugs.launchpad.net/bugs/307306
You received this bug notification
unsubscribe
On Wed, Sep 15, 2010 at 4:43 PM, Bug Watch Updater
307...@bugs.launchpad.net wrote:
** Changed in: gnome-desktop
Importance: Unknown = High
--
upgrade to 2:1.2.99.2-0ubuntu1 makes session utterly slow
https://bugs.launchpad.net/bugs/307306
You received this bug notification
** Tags added: oem-services
--
upgrade to 2:1.2.99.2-0ubuntu1 makes session utterly slow
https://bugs.launchpad.net/bugs/307306
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-desktop in ubuntu.
--
desktop-bugs mailing list
On Mon, 2009-04-27 at 12:35 +, BigBadBassMan wrote:
this also seems to affect vino (vino-server) because disabling it shows
normal behaviour, whereas an enabled vino whill eat up to 70% of CPU on
a Core2Duo E8400 with only Firefox and pidgin opened.
affects vino
status invalid
That
this also seems to affect vino (vino-server) because disabling it shows
normal behaviour, whereas an enabled vino whill eat up to 70% of CPU on
a Core2Duo E8400 with only Firefox and pidgin opened.
** Also affects: vino
Importance: Undecided
Status: New
--
upgrade to
hallo, i have same problem, the status bars cause it, I've attached screenshot
when I use theme without animated status bars, it's better
** Attachment added: Screenshot
http://launchpadlibrarian.net/26017714/Obrazovka.png
--
upgrade to 2:1.2.99.2-0ubuntu1 makes session utterly slow
** Changed in: gnome-desktop
Status: New = Fix Released
--
upgrade to 2:1.2.99.2-0ubuntu1 makes session utterly slow
https://bugs.launchpad.net/bugs/307306
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-desktop in ubuntu.
if killing both gnome-setting-daemon and gnome-power-manager doesn't solve the
problem, please file a new bug report and follow the instructions reported here
to diagnose the problem:
https://wiki.ubuntu.com/X/Troubleshooting/HighCPU
--
upgrade to 2:1.2.99.2-0ubuntu1 makes session utterly slow
I also have had this problem, stopping the mentioned GNOME components
didn't solve the problem, although it did bring the X server CPU usage
down from about 50% to about 20%. I have an IBM ThinkPad X32, with a
ATI Radeon Mobility M6 LY (AGP) 16MB.
--
upgrade to 2:1.2.99.2-0ubuntu1 makes session
I upgraded from Ubuntu 8.10 to 9.04 64bit. Xorg takes 15-30 % CPU all the time
even if it's idle.
lspci | grep VGA
00:02.0 VGA compatible controller: Intel Corporation Mobile GM965/GL960
Integrated Graphics Controller (rev 0c)
** Attachment added: My xorg.conf
** Changed in: gnome-desktop
Status: Fix Released = New
--
upgrade to 2:1.2.99.2-0ubuntu1 makes session utterly slow
https://bugs.launchpad.net/bugs/307306
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-desktop in ubuntu.
I noticed this too, updated today, installed from Jaunty Beta amd64.
Gnome is unusably slow on a dualcore - sucks up between 50-90% idling
from login onwards - this happens every time I log in to Gnome. The
problem is only with Gnome - Im now running XFCE and everything works
right and smooth,
commenting on a closed bug about different issues will not work great
there, you should better open new bugs about your performances issue
with a clear description
--
upgrade to 2:1.2.99.2-0ubuntu1 makes session utterly slow
https://bugs.launchpad.net/bugs/307306
You received this bug
could whoever is subscribed to this bug with an anti-spam service which
replies to comment stop that now?
--
upgrade to 2:1.2.99.2-0ubuntu1 makes session utterly slow
https://bugs.launchpad.net/bugs/307306
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which
That may have been my overzealous spam filter. I've disabled it now.
Sorry for the problem.
--
upgrade to 2:1.2.99.2-0ubuntu1 makes session utterly slow
https://bugs.launchpad.net/bugs/307306
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed
Created new bug here: https://bugs.launchpad.net/ubuntu/+source/gnome-
settings-daemon/+bug/339228
--
upgrade to 2:1.2.99.2-0ubuntu1 makes session utterly slow
https://bugs.launchpad.net/bugs/307306
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
The g-s-d problem caused me to misinterpret a problem with dual-monitor
displays. On a Macbook 1,1 whenever I plugged in a DVI-to-HDMI connector
to a flatscreen television (using a TMDS-1 output on an intel card), on
hotplug the machine would start to slow down. On coldplug and an
unaltered
** Attachment added: Xorg.0.log
http://launchpadlibrarian.net/23571148/Xorg.0.log
--
upgrade to 2:1.2.99.2-0ubuntu1 makes session utterly slow
https://bugs.launchpad.net/bugs/307306
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
Just to be clear, these are the same symptoms that Chousuke reported on
2009-01-26. Running gnome-display-properties will cause the screen to go
black until it's closed, regardless of whether g-s-d is running. A clean
X session with g-s-d disabled at startup and briefly running gnome-
I am getting exactly this problem, still, with the latest jaunty
packages that have claimed to fix it.
If I run gnome-settings-daemon, I get constant ~30% CPU usage.
If I kill gnome-settings-daemon, the problem goes away.
I have another machine also running jaunty which doesn't show the
Undoing re-opening of bug, as some subsequent change seems to have fixed
the problem for real.
** Changed in: gnome-power-manager (Ubuntu)
Status: In Progress = Fix Released
--
upgrade to 2:1.2.99.2-0ubuntu1 makes session utterly slow
https://bugs.launchpad.net/bugs/307306
You received
Undoing re-opening of bug, as some subsequent change seems to have fixed
the problem for real.
** Changed in: gnome-desktop (Ubuntu)
Status: In Progress = Fix Released
--
upgrade to 2:1.2.99.2-0ubuntu1 makes session utterly slow
https://bugs.launchpad.net/bugs/307306
You received this
Bug 324524 filed concerning the g-p-m slow startup and less-than-full-
but-still-abnormal CPU usage.
I don't recall any relevant updates, but the full CPU usage issue which
I refer to in the 2009-01-30 comments no longer reproduces for me, so
I'm happy to close this bug.
--
upgrade to
Re Alberto's last comment - killing g-p-m _does_ solve the issue now
broken out into bug 324524 - I'm absolutely convinced that that one is
g-p-m related.
The issue which g-p-m didn't solve was the full CPU usage which I can no
longer reproduce. Sorry for being less than clear which one I was
** Changed in: xorg-server
Status: Confirmed = Fix Released
--
upgrade to 2:1.2.99.2-0ubuntu1 makes session utterly slow
https://bugs.launchpad.net/bugs/307306
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-desktop in
Max: does killing gnome-settings-daemon solve the problem?
--
upgrade to 2:1.2.99.2-0ubuntu1 makes session utterly slow
https://bugs.launchpad.net/bugs/307306
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-desktop in ubuntu.
--
No, killing gnome-settings-daemon does not affect the CPU usage level,
as mentioned in comment 33 above.
--
upgrade to 2:1.2.99.2-0ubuntu1 makes session utterly slow
https://bugs.launchpad.net/bugs/307306
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which
Ok Max, it must be a different bug then. Please file a new bug report
and explain that, differently from this bug, killing gnome-settings-
daemon and gnome-power-manager doesn't solve the problem.
--
upgrade to 2:1.2.99.2-0ubuntu1 makes session utterly slow
https://bugs.launchpad.net/bugs/307306
See also:
https://wiki.ubuntu.com/X/Troubleshooting/HighCPU
--
upgrade to 2:1.2.99.2-0ubuntu1 makes session utterly slow
https://bugs.launchpad.net/bugs/307306
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-desktop in ubuntu.
--
I am reopening the task against gnome-desktop, as in my case, on the
Acer Aspire One, the current 1:2.25.5-0ubuntu1 does _not_ fix the
problem. I require additionally Peter Clifton's workaround from comment
23, a.k.a.
http://bugzilla.gnome.org/attachment.cgi?id=126905action=view, or the
Xorg CPU
closing gnome desktop task. it was fixed in version 1:2.25.5-0ubuntu1
** Changed in: gnome-desktop (Ubuntu)
Status: In Progress = Fix Released
--
upgrade to 2:1.2.99.2-0ubuntu1 makes session utterly slow
https://bugs.launchpad.net/bugs/307306
You received this bug notification because
This bug was fixed in the package gnome-power-manager - 2.24.0-0ubuntu14
---
gnome-power-manager (2.24.0-0ubuntu14) jaunty; urgency=low
* Add 79-randr13-speed-fix.patch from Gnome SVN to use a less expensive
call when operating with xrandr 1.3. Original patch by Alberto
Reversing automated action of Launchpad Janitor, as per my previous
comments the patch improves but does not fully fix the problem with
gnome-power-manager
** Changed in: gnome-power-manager (Ubuntu)
Status: Fix Released = In Progress
--
upgrade to 2:1.2.99.2-0ubuntu1 makes session
Some additional information on my problems reported in comment 33:
(which, to recap, are that gnome-power-manager still stimulates Xorg
into using excessive CPU with the patches applied, but not as excessive
as without them, and that the CPU usage stops after a while)
I turned off autostart of
i am completely up-to-date but still having problems whenever the screen
brightness changes, even if it's a manual change by me (i.e., using the
Macbook brightness buttons) ...
--
upgrade to 2:1.2.99.2-0ubuntu1 makes session utterly slow
https://bugs.launchpad.net/bugs/307306
You received this
I noticed that running the gnome-display-properties application also
triggers this; I was able to consistently trigger this bug by:
1) first having my external monitor unplugged
2) plugging it in; at this point, nothing happens.
3) start gnome-display-properties - X.org goes insane and the
Xorg on my also used 100% of one of cores. But I was not able to solve this
without recompiling packages.
* Nothing changed if I killed gnome-power-manager or gnome-settings-daemon.
* I downgraded libxrandr to intrepid version, and the related packages - no
change.
* Removed
Just started happening to me a couple days after I upgraded to jaunty,
didn't seem to be any updates that triggered it.
Consistently occurred for 3 reboots, going away when I switched to vesa,
and coming back when switching back to intel, and then mysteriously
disappeared again just as I was
Max: what driver are you using?
Carey: it depends on RandR events. Vesa doesn't support them.
--
upgrade to 2:1.2.99.2-0ubuntu1 makes session utterly slow
https://bugs.launchpad.net/bugs/307306
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
intel / dri i915 - I'll attach Xorg.0.log
Though, I've now noticed that about 2 and a half minutes after login,
the rogue CPU usage stops. (In comparison to stopping immediately if I
kill gnome-power-manager).
** Attachment added: Xorg.0.log
http://launchpadlibrarian.net/21537221/Xorg.0.log
** Bug watch added: GNOME Bug Tracker #568537
http://bugzilla.gnome.org/show_bug.cgi?id=568537
** Also affects: libgnome via
http://bugzilla.gnome.org/show_bug.cgi?id=568537
Importance: Unknown
Status: Unknown
--
upgrade to 2:1.2.99.2-0ubuntu1 makes session utterly slow
I have provided upstream with Peter's patch (after testing it) and I've also
written another patch so as to make sure that gnome-desktop checks the version
of the library at runtime too:
http://bugzilla.gnome.org/show_bug.cgi?id=568537
** Changed in: libgnome
Importance: Unknown = Undecided
I'm afraid that for me, the bug still exists even after rebuilding
gnome-desktop with
http://bugzilla.gnome.org/attachment.cgi?id=126905action=view from
http://bugzilla.gnome.org/show_bug.cgi?id=568160, and rebuilding gnome-
power-manager with
** Changed in: gnome-desktop
Status: New = Fix Released
** Changed in: gnome-power
Status: New = Fix Released
--
upgrade to 2:1.2.99.2-0ubuntu1 makes session utterly slow
https://bugs.launchpad.net/bugs/307306
You received this bug notification because you are a member of Ubuntu
This bug was fixed in the package gnome-desktop - 1:2.25.5-0ubuntu1
---
gnome-desktop (1:2.25.5-0ubuntu1) jaunty; urgency=low
* New upstream version:
libgnome-desktop
- GnomeBG: use gdk_color_equal() instead of custom function
- GnomeRR: use XRRGetScreenResourcesCurrent
I've added comments on the upstream bugs to point out that the fix isn't
quite correct.
Testing the Xrandr client library for version at compile time is
necessary, but you also need to test the reported Xrandr protocol
version from the server, since in the general case, the two might not
match.
It would be a problem only if one downgraded libxrandr to a previous
version. Usually distributions don't update libxrandr or the Xserver in
stable releases. This means that g-d and g-p-m will have to be rebuilt
(in this case) in order to be used with previous versions of libxrandr.
In any case
It would be a problem only if one downgraded libxrandr to a previous version.
Usually distributions don't update
libxrandr or the Xserver in stable releases. This means that g-d and g-p-m
will have to be rebuilt (in this case) in order to be used with previous
versions of libxrandr. In any
Also, unfortunately the problem isn't fixed by the cheaper call to
XRRGetScreenResourcesCurrent
Other Xrandr calls are expensive, such as the XRRGetScreenSizeRange
one made in gnome-desktop's gnome-rr.c
This Xserver backtrace shows the issue:
#0 0xb809e430 in __kernel_vsyscall ()
#1
My local kludgy workaround for now is this:
-- gnome-desktop-2.25.5.orig/libgnome-desktop/gnome-rr.c
+++ gnome-desktop-2.25.5/libgnome-desktop/gnome-rr.c
@@ -512,6 +512,8 @@
switch (event-subtype)
{
+case RRNotify_OutputProperty:
+return
I'm curious to know more on how gnome-power-manager and gnome-settings-
daemon are used remotely so as to better define the use-case in which
this change would lead to a failure.
It's weird that I can't reproduce the problem any longer (even with
XRRGetScreenSizeRange).
I have a few questions:
These programs might be used remotely, or in a nested X session, or a
VNC session, for example. I realise there are ways and means, but I
suspect the stock VNC server from RealVNC won't support that extension
(theory untested).
I have in the past (not currently) run servers hosting desktops,
gnome-power-manager isn't bothering me, since I still have the patched
version of GDK which isn't emitting the monitors-changed event for
output property notifications.
gdkevents-x11.c, line 2114:
if (screen notify-subtype != RRNotify_OutputProperty)
Blocking out XRRGetScreenSizeRange does indeed also fix the problem,
however I noted that the call fills in information which may be accessed
via various APIs, so I'd prefer to leave it in there if possible.
At least, disabling the update when recieving an output property
notification just means
This is most easily reproducible if you have a laptop, remove / insert
the AC lead, and wait some seconds before gnome-power-manager notices,
and starts to fade the backlight brightness between its AC and battery
presets.
Killing gnome-settings-daemon fixes the issue (or patching it as above).
** Changed in: gnome-desktop (Ubuntu)
Status: Fix Released = In Progress
--
upgrade to 2:1.2.99.2-0ubuntu1 makes session utterly slow
https://bugs.launchpad.net/bugs/307306
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
I set the report to in progress.
Your workaround shouldn't cause any problem to either the RandR applet
or the g-s-d, therefore I think it would be ok to apply it.
We can ask upstream to adopt the patch and see how it goes. Do you want
me to do this or do you prefer to do it yourself?
--
Sure.. are those the only two consumers of gnome-rr.c's API?
If you're happy to push stuff upstream, please go ahead. I was hoping my
mail to the xorg list ('CC yourself and KeithP) would yield some insight
as to what they consider the best fix.
--
upgrade to 2:1.2.99.2-0ubuntu1 makes session
Ok, thanks for your fix then. I'll discuss this with upstream
--
upgrade to 2:1.2.99.2-0ubuntu1 makes session utterly slow
https://bugs.launchpad.net/bugs/307306
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-desktop in ubuntu.
** Changed in: gnome-desktop
Status: Unknown = New
** Changed in: gnome-power
Status: Unknown = New
--
upgrade to 2:1.2.99.2-0ubuntu1 makes session utterly slow
https://bugs.launchpad.net/bugs/307306
You received this bug notification because you are a member of Ubuntu
Desktop
** Also affects: gnome-desktop (Ubuntu)
Importance: Undecided
Status: New
** Also affects: gnome-power-manager (Ubuntu)
Importance: Undecided
Status: New
** Bug watch added: GNOME Bug Tracker #568162
http://bugzilla.gnome.org/show_bug.cgi?id=568162
** Also affects:
As Peter Clifton pointed out, there's a new and less expensive call in
the RandR 1.3 API (XRRGetScreenResourcesCurrent), credits to him for
telling me about it. This function doesn't make RandR reprobe hardware
and it's definitely the right function to use when listening for events
(at least in
66 matches
Mail list logo
