Bug#664737: [kscreensaver] kscreensaver does not lock screen when returning from parallel session
Package: kscreensaver
Version: 4:4.7.4-2
Severity: important
--- Please enter the report below this line. ---
Kscreensaver lock behaviour is inconsistent. When starting a new paralell KDE
session from within KDE and switching back to the original one the screen is
locked. In case you leave the new session, you return to the original one
unlocked.
How to reproduce this:
1) Start "New Session" from within KDE
2) Approve the dialog which notifies, how to switch sessions and
**that your session will be locked**.
3) [Ctrl][Alt][F7]: Switch back to the original settion
*) The original session gets locked
4) Unlock the original session.
5) [Ctrl][Alt][F8]: Switch to the new session
6) Log in (I've used a guest account and LXDE session)
7) Log out from session
*) The original session will appear, but it is not locked.
--- System information. ---
Architecture: amd64
Kernel: Linux 3.2.0-2-amd64
Debian Release: wheezy/sid
990 testing security.debian.org
990 testing ftp.rfc822.org
800 unstable ftp.rfc822.org
690 testing www.debian-multimedia.org
500 testing deb.opera.com
1 experimental ftp.rfc822.org
--- Package information. ---
Depends (Version) | Installed
========================================-+-===================
kde-runtime | 4:4.7.4-2
libc6 (>= 2.4) | 2.13-27
libgl1-mesa-glx | 7.11.2-1
OR libgl1 |
libglu1-mesa | 7.11.2-1
OR libglu1 |
libkdecore5 (>= 4:4.4.4-2~) | 4:4.7.4-4
libkdeui5 (>= 4:4.3.4) | 4:4.7.4-4
libkexiv2-10 (>= 4:4.7.1) | 4:4.7.4-2
libkio5 (>= 4:4.3.4) | 4:4.7.4-4
libkparts4 (>= 4:4.3.4) | 4:4.7.4-4
libkscreensaver5 (>= 4:4.6.1) | 4:4.7.4-2
libqt4-opengl (>= 4:4.5.3) | 4:4.7.4-2
libqtcore4 (>= 4:4.7.0~beta1) | 4:4.7.4-2
libqtgui4 (>= 4:4.5.3) | 4:4.7.4-2
libstdc++6 (>= 4.1.1) | 4.6.3-1
libx11-6 | 2:1.4.4-4
kde-workspace-bin | 4:4.7.4-2
Recommends (Version) | Installed
======================================-+-==============
kde-window-manager | 4:4.7.4-2
kscreensaver-xsavers (= 4:4.7.4-2) |
Package's Suggests field is empty.
Reply to: