Bug 495169
Summary: | mini_commander_applet ties up X in CPU intensive state | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Tom Horsley <horsley1953> |
Component: | gnome-applets | Assignee: | Ray Strode [halfline] <rstrode> |
Status: | CLOSED WORKSFORME | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | medium | Docs Contact: | |
Priority: | low | ||
Version: | rawhide | CC: | mclasen, rstrode |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2009-04-21 23:09:01 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Tom Horsley
2009-04-10 02:20:01 UTC
Well, I just added mini-commander back to the panel with no problem, logged out and back in with no problem and even rebooted and logged back in with no problem, so it looks like a one time event so far. On the other had, it was doing it again today when I booted into f11 again. I don't have all the debuginfo files loaded, but I attached to it with gdb just to see what I could see and a routine that seemed like it might be important in the list was something with bonobo and timeout in the name. Could there be some problem with some server not being fully initialized at login that is a timing dependent thing which makes this bug random? Maybe the faster startup work in f11 has gotten a little carried away? (Just random theories). Also I noticed in the panel that the area where the command line would normally appear was constantly flickering like it was drawing itself, dying, and drawing itself again about as fast as it possibly could. I've yum updateed quite a few updates since I reported this, and I have not seen this behavior in a while, so maybe one of the updates fixed it (or just changed the timing enough that it no longer happens). Ok, closing for now. |