Bug 276283

Summary:	Scrolling with up/down key in akregator (or kontact's akregator) is slow when ibus is running. Other KDE apps don't have this problem.
Product:	[Applications] akregator	Reporter:	eric <prozac>
Component:	general	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED UNMAINTAINED
Severity:	minor	CC:	prozac
Priority:	NOR
Version:	1.7.0
Target Milestone:	---
Platform:	Arch Linux
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description eric 2011-06-22 20:27:46 UTC

Version:           1.7.0 (using KDE 4.6.3) 
OS:                Linux

Scrolling a feed-message with the up/down key is slow. This happens only when ibus (an application used for Chinese input) is running. Quitting ibus makes scrolling fast again, and starting ibus makes it slow again.

This only happens with akregator (and kontact's akregator) not in kmail, konqueror or rekonq.
The scrolling is slow, not jumpy just slow, it looks like smooth scrolling.
Scrolling is only slow when using the up/down key, scrolling using the mouse is normal.

Reproducible: Always

Steps to Reproduce:
1) Open a big feed-message in akregator or kontact's akregator
2) Scroll up and down using the up/down key and remember the speed
3) Start ibus
4) Repeat step 2

Actual Results:  
The speed of scrolling in step 2 is much faster than in step 4.

Expected Results:  
The speed of scrolling in step 2 and 4 are equal.

Starting akregator with different styles (bespin or oxygen) or graphicssystem (native or raster) has no influence.

When I say ibus is running, I mean the ibus-daemon is started in the background. It is not activated or used, it is just waiting for me to press a hotkey-sequence to make in active.

Comment 1 Jekyll Wu 2011-11-22 13:22:03 UTC

I can reproduce the reported problem using ibus-1.4.0 and akregator-4.7.3. The scrolling speed becomes slower when ibus is configured as the input method and ibus-daemon is running.

Comment 2 Denis Kurz 2016-09-24 19:45:03 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 3 Denis Kurz 2017-01-07 22:48:36 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.