| 1 |
Hello, |
| 2 |
|
| 3 |
This happened once before in Kubuntu, though this time I was more |
| 4 |
alert and know what I did right before this happened. So what did |
| 5 |
transpire? |
| 6 |
|
| 7 |
I sent my laptop into sleep mode via the popup menu on the battery |
| 8 |
monitor in KDE. It did this, however, when the machine came out of |
| 9 |
sleep mode, there was no monitor. It wasn't on. I tried my basic set |
| 10 |
of tricks: try and change the screen brightness; try and switch |
| 11 |
monitors via the key combo on the laptop; close the lid and re-open |
| 12 |
it; press the key combo to turn the monitor off; press the key combo |
| 13 |
to go back to sleep mode (didn't work). |
| 14 |
|
| 15 |
Eventually I picked a button that did work: POWER. The system shut |
| 16 |
down normally! After X11 died, it went back the the framebuffer and |
| 17 |
acted like nothing had happened. |
| 18 |
|
| 19 |
However, right after this, KDE has been acting *really* slow. Much |
| 20 |
slower than it should. # top revealed that artsd, xorg, and kded were |
| 21 |
eating cpu time. This is the same behaviour as on Kubuntu before. I |
| 22 |
suspect the cause was the same, however, I don't remember exactly so I |
| 23 |
won't point fingers. |
| 24 |
|
| 25 |
Do any of you know what this is? Do you think if I recompiled xorg, |
| 26 |
kde, and arts if it'd fix the problem? Or, even better, is there a |
| 27 |
way to axe all the configuration settings and see if that fixes the |
| 28 |
problem? Please help, I think it's affecting Gnome as well (scary!) |
| 29 |
|
| 30 |
Thanks for any input you can give! |
| 31 |
|
| 32 |
-- |
| 33 |
========== GCv3.12 ========== |
| 34 |
GCS d-(++) s+: a? C++ UL+>++++ P+ |
| 35 |
L++ E--- W+(+++) N++ o? K? w--- O? M+ |
| 36 |
V? PS- PE+ Y-(--) PGP- t+++ 5? X R tv-- b+ |
| 37 |
DI+++ D+ G e* h- !r !y |
| 38 |
========= END GCv3.12 ======== |
| 39 |
|
| 40 |
-- |
| 41 |
gentoo-user@g.o mailing list |
Archives