Summary: | kdesktop_lock uses 99% CPU on a remote X11 display (recent cygwin) | ||
---|---|---|---|
Product: | kscreensaver | Reporter: | Vince Negri <vnegri> |
Component: | general | Assignee: | kscreensaver bugs tracking <kscreensaver-bugs-null> |
Status: | RESOLVED WORKSFORME | ||
Severity: | normal | CC: | jayen, nospam14 |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | openSUSE | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
Vince Negri
2005-05-18 17:32:14 UTC
Can you try logging in from another UNIX machine (e.g. without Cygwin) to see if the problem still happens then? Chris, I just tried logging in from another SUSE box (running 9.0) and there was no problem locking and unlocking the session. So it does seem to be cygwin-specific. I realize this is a rather old bug but as it is still listed as open, I thought I would let you know that I am encountering the same (or similar) problem. OS: openSuSE 10.3 KDE: 3.5 (kdebase3-3.5.7-87.5) When running locally, kdesktop_lock behaves just fine but when connected remotely (Windows Vista running Xming 7.3 Xserver) kdesktop_lock consumes 100% CPU on one processor of a dual processor machine. Thanks, Greg Same problem here, too. Xming 6.9.0.31 on XP SP2 to debian 4.0 kde 3.5.5a.dfsg.1-6etch2. please reopen if the problem persists with kde 4.5 |