Bug 194553 - Bug: Popup dialogs don't respond to keybd properly
Summary: Bug: Popup dialogs don't respond to keybd properly
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kontact
Classification: Applications
Component: general (show other bugs)
Version: 1.4.2
Platform: Debian testing Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-05-29 15:53 UTC by Jeffrey
Modified: 2017-01-07 22:11 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jeffrey 2009-05-29 15:53:30 UTC
Version:           1.4.2 (using KDE 4.2.2)
OS:                Linux
Installed from:    Debian testing/unstable Packages

I've filed a bug on Debian about this but they said to report it here:
http://bugs.debian.org/525441

When Kontact 1.4.2 pops up asking me either
"There are conflicting signing preferences for these recipients.  Sign this message?"
or
"The message you have composed seems to refer to an attached file but you have not attached anything.  Do you want to attach a file to your message?"

If I use the keyboard to navigate to the buttons and press either [Spacebar] or [Enter] to select an option (Do not sign, or Do not attach a file), the popup will ignore my selection and automatically ask for my GnuPG key or open a dialog for me to select a file to attach, even if I have picked another option.

As reported in the Debian bug, this does function fine if I make my selection with the mouse.
Comment 1 Jaime Torres 2009-06-15 19:39:04 UTC
I guess this is a dup of bug 190631.
Comment 2 Denis Kurz 2016-09-24 19:30:37 UTC
This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present?

If noone confirms this bug for a Framework-based version of kontact (version 5.0 or later, as part of KDE Applications 15.08 or later), it gets closed in about three months.
Comment 3 Denis Kurz 2017-01-07 22:11:47 UTC
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.