Bug 326493 - kmail working but completely unresponsive to user input
Summary: kmail working but completely unresponsive to user input
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kmail2
Classification: Applications
Component: UI (show other bugs)
Version: unspecified
Platform: Debian stable Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-10-23 12:02 UTC by Florian Schanda
Modified: 2017-01-07 22:45 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 Florian Schanda 2013-10-23 12:02:40 UTC
We are seeing a *very* strange problem. We have a number of identical computers with identical KDE setups from Debian stable.

On one of them, every once in a while kmail stops responding to user input. It has *not* crashed. For example it responds to dbus messages, and the automatic mail check still works (and the user interface is redrawn). However any user input (keyboard, mouse both movement and clicking) is simply not processed, as if it was never sent to the window in question. Other kde and non-kde applications (for example emacs) on that system work fine.

Clicking the "close window" button in the title brings up the "this application is not responding, would you like to kill it" message.

I have never seen anything like it and am at a loss of what to do and how to start debugging this problem. We have tried to identify differences in the setup/usage for that user and came up with two things:
   a) they use focus-follows-mouse
   b) they sometimes login from another computer

W.r.t. (a) we have disabled focus-follows-mouse and the problem still persists.

On (b), they sometimes log in from a different computer and have ignored the message "there is already a running instance of kmail". I thought we eliminate this by making sure no kmail or related kio processess are running and then starting kmail again. Again, the problem still persists.

We have recently tried deleting all config in .kde relating to kmail, but the problem still persists.

Do you have any idea what is going on?

Thanks,
   Florian

Reproducible: Always
Comment 1 Denis Kurz 2016-09-24 18:06:40 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 kmail2 (version 5.0 or later, as part of KDE Applications 15.12 or later), it gets closed in about three months.
Comment 2 Denis Kurz 2017-01-07 22:45:07 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.