Bug 334 - openssh-askpass-qt4 : impossible to get focus during KDE start
Summary: openssh-askpass-qt4 : impossible to get focus during KDE start
Status: RESOLVED INVALID
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: i586 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-03-11 00:24 CET by Samuel Verschelde
Modified: 2011-07-09 19:52 CEST (History)
1 user (show)

See Also:
Source RPM: openssh-askpass-qt4-1.0.1-4.mga1.src.rpm
CVE:
Status comment:


Attachments

Description Samuel Verschelde 2011-03-11 00:24:46 CET
Description of problem:
I use keychain for my ssh passwords, and it asks for a password when the session starts, which is immediately after I type my session login and password.
openssh-askpass-qt4 shows up, but impossible to type in it : there is no way to make the input field get the focus for typing.
I'm then obliged to cancel, and type the password once the KDE session has finished to load, once per tab in konsole :(

Version-Release number of selected component (if applicable):
openssh-askpass-qt4-1.0.1-4.mga1.src.rpm

How reproducible:
always here


Reproducible: 

Steps to Reproduce:
Thierry Vignaud 2011-03-15 09:59:10 CET

CC: (none) => thierry.vignaud
Assignee: bugsquad => ahmadsamir3891

Comment 1 Ahmad Samir 2011-03-15 18:52:11 CET
keychain is configured to, by default, not show the askpass dialogue before the window manager starts c.f. http://svn.mandriva.com/cgi-bin/viewvc.cgi/packages?view=revision&revision=213091

However the gtk and x11 dialogues can work before a window manager start, i.e. they'd work anyway, it's the qt4 dialogue that has this behaviour. I am not sure if this is a qt4/kde4 limitation...

Given the fact that the qt4 dialogue was written/developed by Mandriva (probably Helio wrote it?), I suggest we close this report as invalid (discussing with Samuel on IRC, he was invoking the askpass dialogue manually from ~/.bash_profile), and the OP can open a report upstream about this (again, I am not sure if this is a qt4 limitation).

Assignee: ahmadsamir3891 => bugsquad

Comment 2 Samuel Verschelde 2011-07-09 19:52:58 CEST
no more problem in an install on real hardware

Status: NEW => RESOLVED
Resolution: (none) => INVALID


Note You need to log in before you can comment on or make changes to this bug.