Issue Details (XML | Word | Printable)

Key: FL-2768
Type: Bug Bug
Status: Closed Closed
Resolution: Fixed
Priority: Major Major
Assignee: Distro
Reporter: Berg
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
Foresight Linux

xorg uses 95% CPU after 2-qa update

Created: 25/Jun/11 10:27 AM   Updated: 28/Jun/11 10:59 AM
Component/s: None
Affects Version/s: None
Fix Version/s: None
Security Level: Public (Everyone can see this issue)

Time Tracking:
Not Specified

Environment: 2.6.38.8-1-fl.smp.gcc4.4.x86_64 intel FL:2-qa on a dell E4300


 Description  « Hide
after an updateall, xorg uses >95% of the cpu. The updates proposed by conary are in http://pastebin.com/gSt6m0xi
Meanwhile I created a new user with the default wm settings, and it works well until I set the panel background color to 'solid'. Below is the .xsession-errors I get on that account. I could eventually update all packages one by one until I find the culprit, but the recent update is a challenge for my box.

GNOME_KEYRING_CONTROL=/tmp/keyring-IABdBV
GPG_AGENT_INFO=/tmp/keyring-IABdBV/gpg:0:1
GNOME_KEYRING_CONTROL=/tmp/keyring-IABdBV
GPG_AGENT_INFO=/tmp/keyring-IABdBV/gpg:0:1
SSH_AUTH_SOCK=/tmp/keyring-IABdBV/ssh
GNOME_KEYRING_CONTROL=/tmp/keyring-IABdBV
GNOME_KEYRING_CONTROL=/tmp/keyring-IABdBV

(gnome-panel:2119): GVFS-RemoteVolumeMonitor-WARNING **: invoking IsSupported() failed for remote volume monitor with dbus name
org.gtk.Private.GPhoto2VolumeMonitor: org.freedesktop.DBus.Error.Spawn.ExecFailed: Failed to execute program /usr/libexec/gvfs
-gphoto2-volume-monitor: Success

    • Message: adding killswitch idx 1 state KILLSWITCH_STATE_HARD_BLOCKED
    • Message: killswitch 1 is KILLSWITCH_STATE_HARD_BLOCKED
    • Message: killswitches state KILLSWITCH_STATE_HARD_BLOCKED
    • Message: killswitch 1 is KILLSWITCH_STATE_HARD_BLOCKED
    • Message: killswitches state KILLSWITCH_STATE_HARD_BLOCKED

MCS->Xfconf settings migration complete

    • Message: NumLock remembering disabled because hostname is set to "localhost"

(gnome-settings-daemon:2110): GVFS-RemoteVolumeMonitor-WARNING **: invoking IsSupported() failed for remote volume monitor with
dbus name org.gtk.Private.GPhoto2VolumeMonitor: org.freedesktop.DBus.Error.Spawn.ExecFailed: Failed to execute program /usr/li
bexec/gvfs-gphoto2-volume-monitor: Success

    • Message: applet now removed from the notification area
      warning: No hp: or hpfax: devices found in any installed CUPS queue. Exiting.

HP Linux Imaging and Printing System (ver. 3.10.2)
System Tray Status Service ver. 2.0

Copyright (c) 2001-9 Hewlett-Packard Development Company, LP
This software comes with ABSOLUTELY NO WARRANTY.
This is free software, and you are welcome to distribute it
under certain conditions. See COPYING file for more details.

Initializing nautilus-main-menu extension
Initializing nautilus-gdu extension
Initializing nautilus-open-terminal extension

(nautilus:2121): GVFS-RemoteVolumeMonitor-WARNING **: invoking IsSupported() failed for remote volume monitor with dbus name or
g.gtk.Private.GPhoto2VolumeMonitor: org.freedesktop.DBus.Error.Spawn.ExecFailed: Failed to execute program /usr/libexec/gvfs-gp
hoto2-volume-monitor: Success

    • Message: applet now embedded in the notification area
      [GLX] your GL driver is currently blocked. If you would like to bypass this, define the MOZ_GLX_IGNORE_BLACKLIST environment va
      riable.
      /usr/share/themes/DarkRoom/gtk-2.0/gtkrc:83: Murrine configuration option "gradients" is no longer supported and will be ignore
      d.
      /usr/share/themes/Human/gtk-2.0/gtkrc:82: Murrine configuration option "gradients" is no longer supported and will be ignored.

(gnome-appearance-properties:2366): GLib-WARNING **: GError set over the top of a previous GError or uninitialized memory.
This indicates a bug in someone's code. You must ensure an error is NULL before it's set.
The overwriting error message was: Line 68 character 64: Could not parse "shade/gtk:bg[NORMAL]/0.84" as an integer

(gnome-appearance-properties:2366): GLib-WARNING **: GError set over the top of a previous GError or uninitialized memory.
This indicates a bug in someone's code. You must ensure an error is NULL before it's set.
The overwriting error message was: Line 69 character 66: Could not parse "shade/gtk:bg[NORMAL]/0.80" as an integer

(gnome-appearance-properties:2366): GLib-WARNING **: GError set over the top of a previous GError or uninitialized memory.
This indicates a bug in someone's code. You must ensure an error is NULL before it's set.
The overwriting error message was: Line 70 character 67: Could not parse "shade/gtk:bg[NORMAL]/0.78" as an integer

(gnome-appearance-properties:2366): GLib-WARNING **: GError set over the top of a previous GError or uninitialized memory.
This indicates a bug in someone's code. You must ensure an error is NULL before it's set.
The overwriting error message was: Line 71 character 60: Could not parse "shade/gtk:bg[NORMAL]/0.88" as an integer

(gnome-appearance-properties:2366): GLib-WARNING **: GError set over the top of a previous GError or uninitialized memory.
This indicates a bug in someone's code. You must ensure an error is NULL before it's set.
The overwriting error message was: Line 72 character 63: Could not parse "shade/gtk:bg[NORMAL]/1.12" as an integer

(gnome-appearance-properties:2366): GLib-WARNING **: GError set over the top of a previous GError or uninitialized memory.
This indicates a bug in someone's code. You must ensure an error is NULL before it's set.
The overwriting error message was: Line 73 character 60: Could not parse "shade/gtk:bg[NORMAL]/0.56" as an integer

(gnome-appearance-properties:2366): GLib-WARNING **: GError set over the top of a previous GError or uninitialized memory.
This indicates a bug in someone's code. You must ensure an error is NULL before it's set.
The overwriting error message was: Line 75 character 66: Could not parse "shade/gtk:bg[NORMAL]/0.76" as an integer

(gnome-appearance-properties:2366): GLib-WARNING **: GError set over the top of a previous GError or uninitialized memory.
This indicates a bug in someone's code. You must ensure an error is NULL before it's set.
The overwriting error message was: Line 76 character 64: Could not parse "shade/gtk:bg[NORMAL]/0.81" as an integer
/usr/share/themes/Human/gtk-2.0/gtkrc:82: Murrine configuration option "gradients" is no longer supported and will be ignored.
/usr/share/themes/DarkRoom/gtk-2.0/gtkrc:83: Murrine configuration option "gradients" is no longer supported and will be ignore
d.

 All   Comments   Work Log   Change History      Sort Order: Ascending order - Click to sort in descending order
[ Permalink | « Hide ]
Tomas Forsman added a comment - 26/Jun/11 04:17 PM
What graphic card do you have and do you know what graphic driver you are using?

[ Permalink | « Hide ]
Berg added a comment - 26/Jun/11 05:17 PM
Hi Tomas:

lspci gives:

00:02.0 VGA compatible controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07) (prog-if 00 [VGA controller])
Subsystem: Dell Device 024d
Flags: bus master, fast devsel, latency 0, IRQ 44
Memory at f6c00000 (64-bit, non-prefetchable) [size=4M]
Memory at e0000000 (64-bit, prefetchable) [size=256M]
I/O ports at ef98 [size=8]
Capabilities: [90] MSI: Mask- 64bit- Count=1/1 Enable+
Capabilities: [d0] Power Management version 3
Kernel driver in use: i915
Kernel modules: i915

00:02.1 Display controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07)
Subsystem: Dell Device 024d
Flags: bus master, fast devsel, latency 0
Memory at f6b00000 (64-bit, non-prefetchable) [size=1M]
Capabilities: [d0] Power Management version 3

The driver in xorg.conf is intel

Cheers,


[ Permalink | « Hide ]
António Meireles [aka doniphon] added a comment - 26/Jun/11 05:34 PM
(back from an extended weekend). can you try to update to gtk=foresight.rpath.org@fl:2-devel/2.24.4-2-1 and see if this fixes your issue ?
(i think this is a gtk issue)
Thanxs in advance

[ Permalink | « Hide ]
António Meireles [aka doniphon] added a comment - 26/Jun/11 05:59 PM
i've downgraded in-pace gtk in 2-qa and i'm rebuilding groups there (i don t want to do a promote from 2-devel (which since yesterday has a behaving gtk) as that would imply the landing of the whole xorg bump which for now is 2-devel only). groups are rebuilding and should be finished in the next 2 hrs. plz tell us if ~2 hrs from now an updateall will just fix this

Thanxs for your patience.


[ Permalink | « Hide ]
Berg added a comment - 27/Jun/11 01:24 AM
I will try to do so later, right now I really can't risk going through such a heavy update/rollback again, as I need the box for work..

[ Permalink | « Hide ]
Berg added a comment - 28/Jun/11 03:37 AM
Hi Doniphon, here's the result of my attempt to update gtk

sudo conary update gtk
Troves being installed appear to conflict:
gtk:config > /foresight.rpath.org@fl:2-qa/2.24.4-2-1[~!builddocs is: x86]>/foresight.rpath.org@fl:2-qa/2.24.4-2-1[~!builddocs is: x86_64]
gtk:data > /foresight.rpath.org@fl:2-qa/2.24.4-2-1[~!builddocs is: x86_64]>/foresight.rpath.org@fl:2-qa/2.24.4-2-1[~!builddocs is: x86]
gtk:devel > /foresight.rpath.org@fl:2-qa/2.24.4-2-1[~!builddocs is: x86]>/foresight.rpath.org@fl:2-qa/2.24.4-2-1[~!builddocs is: x86_64]
gtk:doc > /foresight.rpath.org@fl:2-qa/2.24.4-2-1[~!builddocs is: x86_64]>/foresight.rpath.org@fl:2-qa/2.24.4-2-1[~!builddocs is: x86]
gtk:locale > /foresight.rpath.org@fl:2-qa/2.24.4-2-1[~!builddocs is: x86_64]>/foresight.rpath.org@fl:2-qa/2.24.4-2-1[~!builddocs is: x86]
gtk:runtime > /foresight.rpath.org@fl:2-qa/2.24.4-2-1[~!builddocs is: x86_64]>/foresight.rpath.org@fl:2-qa/2.24.4-2-1[~!builddocs is: x86]


[ Permalink | « Hide ]
António Meireles [aka doniphon] added a comment - 28/Jun/11 05:15 AM
try plz sudo conary update gtk=@fl:2-qa[is:x86_64] gtk:lib=@fl:2-qa[is:x86]

[ Permalink | « Hide ]
Berg added a comment - 28/Jun/11 06:32 AM
That worked well.

I don't get the conflict message afterwards when updating the rest of gtk (unless that's not necessary?) but then I get:

sudo conary update gtk=@fl:2-qa
Applying update job:
Update gtk (2.24.4-1-1[~!builddocs] -> 2.24.4-2-1[~!builddocs])
Install gtk:config=2.24.4-2-1[~!builddocs]
Install gtk:data=2.24.4-2-1[~!builddocs]
Install gtk:devel=2.24.4-2-1[~!builddocs]
Install gtk:devellib=2.24.4-2-1[~!builddocs]
Install gtk:doc=2.24.4-2-1[~!builddocs]
Install gtk:locale=2.24.4-2-1[~!builddocs]
Install gtk:runtime=2.24.4-2-1[~!builddocs]
Creating database transaction (8 of 8)...changeset cannot be applied:
applying update would cause errors:
/usr/bin/gtk-demo conflicts with a file owned by gtk:runtime=/foresight.rpath.org@fl:2-qa/2.24.4-2-1[~!builddocs is: x86_64]

/usr/bin/gtk-update-icon-cache conflicts with a file owned by gtk:runtime=/foresight.rpath.org@fl:2-qa/2.24.4-2-1[~!builddocs is: x86_64]

/etc/conary/tags/gtk-input-method conflicts with a file owned by gtk:runtime=/foresight.rpath.org@fl:2-qa/2.24.4-2-1[~!builddocs is: x86_64]


[ Permalink | « Hide ]
António Meireles [aka doniphon] added a comment - 28/Jun/11 06:37 AM
just do an updateall . will get what you want.

[ Permalink | « Hide ]
Berg added a comment - 28/Jun/11 10:59 AM
xorg use back to normal after an updateall. Issue closed on this one - thanks!

[ Permalink | « Hide ]
Berg added a comment - 28/Jun/11 10:59 AM
gtk fix seems to have worked!


Powered by a free Atlassian JIRA open source license for Foresight Linux. Try JIRA - bug tracking software for your team.
Atlassian JIRA the Professional Issue Tracker. (Enterprise Edition, Version: 3.13.5-#360) - Bug/feature request - Atlassian news - Contact Administrators