Bug 214348 - KMail keyboard stops working after desktop lock / unlock
Summary: KMail keyboard stops working after desktop lock / unlock
Status: RESOLVED DUPLICATE of bug 206860
Alias: None
Product: kmail
Classification: Unmaintained
Component: general (show other bugs)
Version: 1.12.2
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-11-13 04:57 UTC by David Gersic
Modified: 2010-03-06 23:38 UTC (History)
2 users (show)

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 David Gersic 2009-11-13 04:57:26 UTC
Version:           1.12.2 (using KDE 4.3.1)
OS:                Linux
Installed from:    openSUSE RPMs

Initially, KMail keyboard navigation works fine. If I lock / unlock the desktop session, KMail stops responding to keyboard navigation, but otherwise is still working. Typing messages works, for example, but ctrl-n to send a new message does not. Exiting and restarting KMail gets keyboard navigation working again.

This is 100% repeatable. If any other information is needed, I'd be happy to supply it.

OS is OpenSUSE 11.1 Linux, using Gnome as the desktop, but with KMail as the email package.
Comment 1 Martin Koller 2009-11-21 17:18:18 UTC
Can you check if you have the same problem with any other KDE application in that situation (which was running before you lock the screen) ?
Comment 2 David Gersic 2009-11-25 02:20:37 UTC
I don't use any other KDE apps, just KMail. Is there one in particular that you'd like me to test this with?
Comment 3 Martin Koller 2009-11-25 08:01:36 UTC
Try kwrite for example.
Comment 4 David Gersic 2009-11-26 20:04:45 UTC
Ok, tested with kwrite and here's the results. I left kmail and kwrite running. kmail was left as the foreground application. After the screensaver locked and was unlocked, kmail was affected. Switched to kwrite, and it was _not_ affected. Switched back to kmail, and it's ok now.

I'm re-testing now leaving kwrite as the foreground application.
Comment 5 David Gersic 2009-11-26 22:14:29 UTC
Kwrite doesn't seem to be able to reproduce the problem. And once kwrite works, kmail is ok as well.
Comment 6 Björn Ruberg 2010-03-06 23:38:34 UTC

*** This bug has been marked as a duplicate of bug 206860 ***