|
Bugzilla – Full Text Bug Listing |
| Summary: | gnome-session causes X to run with high cpu usage | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 11.1 | Reporter: | Istvan Szabo <szaboistvan007> |
| Component: | GNOME | Assignee: | E-mail List <gnome-bugs> |
| Status: | RESOLVED FIXED | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Normal | ||
| Priority: | P5 - None | CC: | captain.magnus |
| Version: | Final | ||
| Target Milestone: | --- | ||
| Hardware: | x86-64 | ||
| OS: | openSUSE 11.1 | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Istvan Szabo
2009-05-10 11:54:41 UTC
Can you try to install the xorg-x11-server from http://widehat.opensuse.org/repositories/home:/MBoman/openSUSE_11.1/ That's what I'm using and I don't see these issues. I have tried that too, but it doesn't solves the problem for me (with vino-server running I still get high cpu) I see a similar issue with KDE and the Xorg process of an idle user having a high CPU usage. I presume this is the same story. I installed the xorg-x11-server suggested above to see if it helps. Time will tell (or I will). I cleared the needinfo flag as I suppose Istvan just forgot to do it. (In reply to comment #1) > Can you try to install the xorg-x11-server from > http://widehat.opensuse.org/repositories/home:/MBoman/openSUSE_11.1/ > > That's what I'm using and I don't see these issues. Doesn't solve the issue for me either. I'm not sure you are having the same problem as I do, because I think this is related to gnome only. But maybe not. Anyways i have found a workaround for the problem: turning off vino-server. So at this stage I cannot decide what causes the problem, the gnome-session, the xorg-x11-server or vino-server? (In reply to comment #4) > (In reply to comment #1) > > Can you try to install the xorg-x11-server from > > http://widehat.opensuse.org/repositories/home:/MBoman/openSUSE_11.1/ > > > > That's what I'm using and I don't see these issues. > > Doesn't solve the issue for me either. Installing the latest update fixed this problem |