Bug 334996

Summary: Touchscreen input not detected properly
Product: [Applications] kmail2 Reporter: bginsburg <zekeb>
Component: UIAssignee: kdepim bugs <kdepim-bugs>
Status: RESOLVED UNMAINTAINED    
Severity: normal CC: zekeb
Priority: NOR    
Version: 4.13   
Target Milestone: ---   
Platform: unspecified   
OS: Linux   
Latest Commit: Version Fixed In:

Description bginsburg 2014-05-18 19:18:18 UTC
I am running kubuntu 14.04 on an acer iconia tab w500. I have the eGalax proprietary driver installed, and multitouch is partially working with ginn (no pinch to zoom yet, but 2-finger scroll and long press for right-click works). On all other programs, the touchscreen seems to perform adequately, including other elements of Kontact. So, for example, clicking on a date in Calendar selects that date - clicking on an event selects that event and double clicking it opens the editor.

However, in Kmail, clicks with the touchscreen only seem to hover the cursor. I can't move the scroll bar (they become outlined, but don't move) and I cant select any element inside of the boxes. So, I can't select a favorite folder, when I try, the whole favorite folder box is highlighted and nothing happens. Same behavior for the message list - I click on a message, and I just see a breif synopsis of the message, it is not selected or preveiwed. I can scroll through the message list with a 2-finger scroll though.

A USB mouse works as expected.


Reproducible: Always

Steps to Reproduce:
1.Open kmail
2. Try to select a message from the message list with the touchscreen
3. Try to select a facorite folder with the touchscreen
Actual Results:  
kmai registers touch as a move and hover.  Not as a left click at the new cursor location

Expected Results:  
Messge or folder would be selected,.

USB mouse works as expected
All other components of Kontact work as expected with the touchscreen
Comment 1 Denis Kurz 2016-09-24 18:14:44 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 21:28:09 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.