Bug 188841

Summary:	akregator nearly unusable with tablet
Product:	[Applications] akregator	Reporter:	M G Berberich <kde>
Component:	general	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED UNMAINTAINED
Severity:	normal	CC:	code
Priority:	NOR
Version:	1.4.1
Target Milestone:	---
Platform:	unspecified
OS:	Linux
Latest Commit:		Version Fixed In:

Description M G Berberich 2009-04-04 23:50:56 UTC

Version:           1.4.1 (using 4.2.1 (KDE 4.2.1), Debian packages)
Compiler:          cc
OS:                Linux (i686) release 2.6.26-1-686

when akregator is used on a tablet-PC,  akregator behaves strange.
In the artikle-list every 2nd click selects a region, and in the sources-list entries are often moved around.

Comment 1 M G Berberich 2009-04-05 17:40:36 UTC

• tests with a usb-wacom-tablet (not a tablet-PC) yields the same result
• kde3 akregator works normal
• gimp, inkscape, xournal work normal.

There are some signs (sometimes the scrollbar-events are duplicated), that this is more a kde4 problem than a akregator-problem, maybe a Qt4.5-Problem.

Comment 2 Martin Zuther 2009-11-15 15:57:37 UTC

System:  Kubuntu Karmic 9.10
Linux:   2.6.31-14 (i386)
KDE:     4.3.2
Tablet:  Wacom Intuos 3 (USB)

I have a similar problem that is probably related.  When I open "Akregator" and double-click on a tab to change the sorting of articles, nothing happens (except that the tab blinks once).  Using the Wacom mouse that came with my tablet doesn't work any better, whereas my USB mouse works as expected.

The same problem occurs in the password safe "KeePassX" when trying to change the sorting of entries.  BTW, I had the same problems running Ubuntu (i.e. GNOME).

Martin

Comment 3 Denis Kurz 2016-09-24 19:43:53 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 akregator (version 5.0 or later, as part of KDE Applications 15.08 or later), it gets closed in about three months.

Comment 4 Denis Kurz 2017-01-07 21:27:48 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.