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

Bug#585043: marked as done (Cannot type password when run from .kde/env during KDE startup)

Your message dated Wed, 15 Mar 2017 11:09:19 +0100
with message-id <20170315100912.ynp7kgoizw3spl2u@gnuservers.com.ar>
and subject line Re: Bug#585043: Cannot type password when run from .kde/env during KDE startup
has caused the Debian Bug report #585043,
regarding Cannot type password when run from .kde/env during KDE startup
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
585043: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=585043
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: ksshaskpass
Version: 0.5.3-1
Severity: important

Hello,
When ksshaskpass is spawned by program running during early KDE startup
it is impossible to type the password.

I've following scriptlet in .kde/env:

$ cat 01ssh-add.sh 
/usr/bin/ssh-add
$ 

During startup I can see ksshaskpass window, it even got focus (slightly blue
frame round the text input field), but no keystrokes are registered. 

No black dots are visible during typing the password. No key is added
to ssh-agent. The ksshaskpass window, however, can react to <Enter> key.
It looks like only text input field is handicapped.

I noticed the problem some time ago. It was either when I upgraded KDE
from 4:4.3.4-1 to 4:4.4.3-1 or from 4:4.4.3-1 to 4:4.4.3-2.

At the moment I am running current sid and the problem still exists.

Regards
	Artur

-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.32-5-amd64 (SMP w/1 CPU core)
Locale: LANG=C, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages ksshaskpass depends on:
ii  kdebase-runtime               4:4.4.4-1  runtime components from the offici
ii  kdelibs5                      4:4.4.4-1  transitional package for the KDE D
ii  libc6                         2.11.1-2   Embedded GNU C Library: Shared lib
ii  libqtcore4                    4:4.6.2-5  Qt 4 core module
ii  libqtgui4                     4:4.6.2-5  Qt 4 GUI module
ii  openssh-client                1:5.5p1-4  secure shell (SSH) client, for sec

Versions of packages ksshaskpass recommends:
ii  kwalletmanager                4:4.4.4-1  secure password wallet manager for

ksshaskpass suggests no packages.

-- no debconf information

-- 
Artur R. Czechowski <arturcz@hell.pl>
GCS/IT dpu-(++) s-:-- a C++ UL++++$ P+++ L++(+++) E--- W++ N+(-) K- w
!O M- V? PE++ Y+ PGP++ t !5 X R tv--(-) b++ DI+++ D+ G e-(*) h++(---) r++ y+

--- End Message ---
--- Begin Message --- 
¡Hola Artur!

El 2010-06-08 a las 18:23 +0200, Artur R. Czechowski escribió:
Package: ksshaskpass Version: 0.5.3-1 Severity: important
Hello, When ksshaskpass is spawned by program running during early KDE startup it is impossible to type the password. 


I've following scriptlet in .kde/env:
Sorry for taking so long to get back to you. Sadly this was the wrong location to launch an interactive application. The scripts in ~/.kde/env are executed before the desktop environment, in particular, before the window manager, as such the shown window is unable gain the required focus.
The script should be placed in ~/.kde/Autostart (or in ~/.config/autostart-scripts/ in later versions).
$ cat 01ssh-add.sh /usr/bin/ssh-add $ 

Happy hacking,
--
"The first 90% of the code accounts for the first 90% of the development time.
The remaining 10% of the code accounts for the other 90% of the development
time."
-- Tom Cargill
Saludos /\/\ /\ >< `/

Attachment: signature.asc
Description: PGP signature


--- End Message ---
Reply to: