| Summary: | kdesktop_lock forkbombs when locking my desktop | ||
|---|---|---|---|
| Product: | [Unmaintained] kscreensaver | Reporter: | Torrie Fischer <tdfischer> |
| Component: | general | Assignee: | kscreensaver bugs tracking <kscreensaver-bugs-null> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | normal | CC: | finex |
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Fedora RPMs | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
Torrie Fischer
2006-10-11 12:57:05 UTC
This behavior happens regardless of graphics card. If you have two screens configured with X, which are NOT connected using xinerama, kdesktop_lock behaves this way. You can also forcefully generate this state by trying to launch kdesktop_lock several times (i.e. from a console). But here, sometimes it succeeds and sometimes not. I observed this behavior with all KDE releases from about 3.4 up to 3.5.5 (using always Debian packages). Therefore, I am forced to use xscreensaver. Additional data: I never ran into this problem running KUbuntu Dapper Drake, but just started experiencing it while running Debian Etch. I used the same xorg.conf file on each system (and the same hardware). We have a Gentoo user reporting this problem as well. To have the problem, this is the configuration you must have : - use KDE - use the multi-screen mode in X (one graphic card supporting multi-screens) - Don't use Xinerama (multi-desktop mode) - run the shell command : kdesktop_lock --forcelock This command runs kdesktop_lock which locks your screens. If you have configured that you want a lock screen after n minutes of idle in your KDE control center, every n minutes the process kdesktop will try to run another kdesktop_lock that should stop, because your screens are already locked. But it does not, every n minutes a kdesktop_lock process will remain in memory, and a screensaver process (blank, for example) will remain too in memory. If you let your station all the night like this, in the morning, you have so many kdesktop_lock processes that the station is overloaded and unlocking your station is quite impossible, you just have to reboot it. Same problem but only when the system goes into screensaver mode with the cursor in the second console screen or lockbutton pressed from the second console screen openSuse 64bit nvidia oh yeah this is KDE 3.5.7 This started happening for me after upgrade from X.Org 6.9.0 to modular X.Org 7.2, on NetBSD/i386. KDE 3.5.8. See also bug 89985. Kdesktop is no more mantained. Fortunatly this bug seems not to be valid for KDE 4. Please reopen if this bug is not a kdesktop one (and it is not solved) or it can be reproduced on KDE 4. Reopened, maybe it is not a kdesktop bug, moved to kscreensaver which could be more appropriate. Anyway I'm not sure this bug will be fixed on KDE 3. *** This bug has been marked as a duplicate of bug 89985 *** |