[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#288923: marked as done (/usr/bin/kdesktop_lock: (KDE bug 96432) impossible to unlock after 1 click, with kxkb enabling >1 layout)



Your message dated Mon, 7 Feb 2005 08:43:15 +0200 (IST)
with message-id <Pine.LNX.4.44.0502070841100.20467-100000@stalker.iGuide.co.il>
and subject line [Bug 96432] kdesktop_lock impossible to unlock after 1 click, with kxkb enabling >1 layout (fwd)
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--------------------------------------
Received: (at submit) by bugs.debian.org; 6 Jan 2005 11:28:02 +0000
>From vassilii@tarunz.org Thu Jan 06 03:28:02 2005
Return-path: <vassilii@tarunz.org>
Received: from mxout2.netvision.net.il [194.90.9.21] 
	by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
	id 1CmVoA-0006io-00; Thu, 06 Jan 2005 03:28:02 -0800
Received: from Ilmarinen ([212.235.30.82]) by mxout2.netvision.net.il
 (Sun Java System Messaging Server 6.1 HotFix 0.06 (built Nov 11 2004))
 with ESMTP id <0I9W00LDV7S8F800@mxout2.netvision.net.il> for
 submit@bugs.debian.org; Thu, 06 Jan 2005 13:26:38 +0200 (IST)
Received: from vassilii by Ilmarinen with local (Exim 4.34)
	id 1CmVmi-0000dE-E5; Thu, 06 Jan 2005 13:26:32 +0200
Date: Thu, 06 Jan 2005 13:26:32 +0200
From: Vassilii Khachaturov <vassilii@tarunz.org>
Subject: /usr/bin/kdesktop_lock: (KDE bug 96432) impossible to unlock after 1
 click, with kxkb enabling >1 layout
Sender: Vassilii Khachaturov <vassilii@tarunz.org>
To: Debian Bug Tracking System <submit@bugs.debian.org>
Message-id: <E1CmVmi-0000dE-E5@Ilmarinen>
MIME-version: 1.0
X-Mailer: reportbug 3.2
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Delivered-To: submit@bugs.debian.org
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 
	(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE 
	autolearn=no version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level: 

Package: kdesktop
Version: 4:3.3.1-3
Severity: normal
File: /usr/bin/kdesktop_lock

(Copy of the report submitted upstream):

I have >1 layout enabled in my kxkb, namely, us (the main one), ru and il.

When I select the lock screen action from the Kde menu, kdesktop_lock
gets started, and the unlock dialog contains a small button with "us".
If I (or, much worse, some adversary against whom the lock is started)
clicks this button, there is no way to unlock the screen again (other
than going to a text console and killing the kdesktop_lock process): the
"us" is changed to "ru", then to "il", then to "err", where it stays. If
I press "cancel", and move the mouse to make the dialog reappear, it
comes back again with "il". The keyboard accelerator for changing the
keyboard layout (that normally works within the KDE session, changing
the little flag in the tray) doesn't work in the unlock dialog.

Expected behaviour: support the keyboard accelerators for changing the
layout, allow circular changing of the layouts via the button in the
unlock dialog. 


-- System Information:
Debian Release: 3.1
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.4.27-1-686
Locale: LANG=ru_RU.KOI8-R, LC_CTYPE=ru_RU.KOI8-R (charmap=KOI8-R)

Versions of packages kdesktop depends on:
ii  kdebase-bin               4:3.3.1-3      KDE Base (binaries)
ii  kdelibs4                  4:3.3.1-4      KDE core libraries
ii  libart-2.0-2              2.3.16-6       Library of functions for 2D graphi
ii  libc6                     2.3.2.ds1-20   GNU C Library: Shared libraries an
ii  libfam0c102               2.7.0-6        client library to control the FAM 
ii  libgcc1                   1:3.4.3-6      GCC support library
ii  libice6                   4.3.0.dfsg.1-8 Inter-Client Exchange library
ii  libidn11                  0.5.2-3        GNU libidn library, implementation
ii  libjpeg62                 6b-9           The Independent JPEG Group's JPEG 
ii  libkonq4                  4:3.3.1-3      Core libraries for KDE's file mana
ii  libpcre3                  4.5-1.1        Perl 5 Compatible Regular Expressi
ii  libpng12-0                1.2.8rel-1     PNG library - runtime
ii  libqt3c102-mt             3:3.3.3-7      Qt GUI Library (Threaded runtime v
ii  libsm6                    4.3.0.dfsg.1-8 X Window System Session Management
ii  libstdc++5                1:3.3.5-5      The GNU Standard C++ Library v3
ii  libx11-6                  4.3.0.dfsg.1-8 X Window System protocol client li
ii  libxext6                  4.3.0.dfsg.1-8 X Window System miscellaneous exte
ii  libxrender1               0.8.3-7        X Rendering Extension client libra
ii  xlibs                     4.3.0.dfsg.1-8 X Window System client libraries m
ii  zlib1g                    1:1.2.2-3      compression library - runtime

-- no debconf information

---------------------------------------
Received: (at 288923-done) by bugs.debian.org; 7 Feb 2005 06:43:19 +0000
>From vassilii@tarunz.org Sun Feb 06 22:43:19 2005
Return-path: <vassilii@tarunz.org>
Received: from res2.iguide.co.il (stalker.iGuide.co.il) [194.90.246.244] (root)
	by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
	id 1Cy2cA-0007kI-00; Sun, 06 Feb 2005 22:43:19 -0800
Received: from stalker.iGuide.co.il (vassilii@localhost [127.0.0.1])
	by stalker.iGuide.co.il (8.12.3/8.12.3/Debian-7.1) with ESMTP id j176hFbf020481
	for <288923-done@bugs.debian.org>; Mon, 7 Feb 2005 08:43:16 +0200
Received: from localhost (vassilii@localhost)
	by stalker.iGuide.co.il (8.12.3/8.12.3/Debian-7.1) with ESMTP id j176hFDu020477
	for <288923-done@bugs.debian.org>; Mon, 7 Feb 2005 08:43:15 +0200
Date: Mon, 7 Feb 2005 08:43:15 +0200 (IST)
From: Vassilii Khachaturov <vassilii@tarunz.org>
Sender: vassilii@stalker.iGuide.co.il
To: 288923-done@bugs.debian.org
Subject: [Bug 96432] kdesktop_lock impossible to unlock after 1 click, with
 kxkb enabling >1 layout (fwd)
Message-ID: <Pine.LNX.4.44.0502070841100.20467-100000@stalker.iGuide.co.il>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Delivered-To: 288923-done@bugs.debian.org
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 
	(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-3.0 required=4.0 tests=BAYES_00 autolearn=no 
	version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level: 

Enclosed is my posting upstream, closing the bug upon retesting after
pulling in KDE 4:3.3.2-1.

---------- Forwarded message ----------
Date: 7 Feb 2005 06:39:52 -0000
From: Vassilii Khachaturov <vassilii@tarunz.org>
Reply-To: 96432@bugs.kde.org
To: vassilii@tarunz.org
Subject: [Bug 96432] kdesktop_lock impossible to unlock after 1 click,
     with kxkb enabling >1 layout

------- You are receiving this mail because: -------
You reported the bug, or are watching the reporter.
You are a voter for the bug, or are watching someone who is.

http://bugs.kde.org/show_bug.cgi?id=96432
vassilii tarunz org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|                            |WORKSFORME



------- Additional Comments From vassilii tarunz org 2005-02-07 07:39 -------
1) minor correction: I actually had us_intl enabled as well at the
time of my original report. "us_intl" was never shown, though, just "err".

2) having pulled in the most recent Debian testing upgrade and retesting
the bug, which caused kdesktop and the kdelibs upgraded to the 4:3.3.2-1
branch, I discovered that the bug no longer happens as described. The
keyboard accelerators still don't work, but with the mouse it is possible
to change them circularly, and thus a malicious bystander can no longer
lockout the user who locked the screen.

Thanks for fixing it this way. I think that the problem is no longer worth
a bug. If you feel that my initial idea that the keyboard accelerators
should be working in the kdesktop_lock passwd entry dialog as well still
needs implementing, feel free to reopen.



Reply to: