Bug 105897 - kdesktop_lock uses 99% CPU on a remote X11 display (recent cygwin)
Summary: kdesktop_lock uses 99% CPU on a remote X11 display (recent cygwin)
Status: RESOLVED WORKSFORME
Alias: None
Product: kscreensaver
Classification: Miscellaneous
Component: general (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: kscreensaver bugs tracking
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-05-18 17:32 UTC by Vince Negri
Modified: 2010-10-23 21:01 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Vince Negri 2005-05-18 17:32:14 UTC
Version:            (using KDE KDE 3.3.0)
Installed from:    SuSE RPMs
Compiler:          gcc 3.3.4 
OS:                Linux

I am logging into a SUSE 9.2 pro desktop using the X.org X11 client provided with cygwin (XWin v6.8.2.0-1)

Everything works pretty well, including screensavers, except for locking the desktop.

On selecting "Lock Session" from the KMenu, the chosen screensaver starts up and runs; however, on moving the mouse/touching a key the unlocking dialogue appears and the kdesktop_lock process begins using all CPU.

.xsession-errors shows:

DCOPReply<>: cast to 'QStringList' error
DCOPReply<>: cast to 'QString' error
Xlib: extension XFree86-Misc missing on display "redacted.my.lan:0.0"
Error: BadAccess (attempt to access private resource denied) 10
Major opcode: 2
Minor opcode: 0
Resource id: 0x2600007


logging in on another terminal and killing the kdesktop_lock process (with -9) gets my desktop back. It appears that the error returned by the cygwin XWin server throws kdesktop_lock into a tight loop?
Comment 1 Chris Howells 2005-06-16 01:41:15 UTC
Can you try logging in from another UNIX machine (e.g. without Cygwin) to see if the problem still happens then?
Comment 2 Vince Negri 2005-06-16 09:37:10 UTC
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.
Comment 3 Greg Downing 2008-12-01 15:35:05 UTC
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
Comment 4 Jayen Ashar 2009-02-04 04:15:20 UTC
Same problem here, too.  Xming 6.9.0.31 on XP SP2 to debian 4.0 kde 3.5.5a.dfsg.1-6etch2.
Comment 5 Oswald Buddenhagen 2010-10-23 21:01:47 UTC
please reopen if the problem persists with kde 4.5