FS#38021 - Non GTK apps behave unresponsively

Attached to Project: Arch Linux
Opened by Robert Orzanna (orschiro) - Thursday, 05 December 2013, 12:00 GMT
Last edited by Allan McRae (Allan) - Thursday, 02 January 2014, 05:13 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To No-one
Architecture x86_64
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

I have a very serious issue here with my non GTK apps.

Their GUIs are very unresponsive and show all few seconds very annoying lags. For instance when I am typing text, I see the text being written about a second later. When I select text, I see the text being highlighted about a second later. And so on.

I experienced this unresponsiveness in Skype, Qtconfig, Virtualbox and Sublime Text 3.

Additional info:
* package version(s)
* config and/or log files etc.

No relevant entries in `journalctl`.

Output of htop when running non GTK apps: http://i.imgur.com/IKFUhaK.png
Output of iotop: http://i.imgur.com/UjqBga7.png

~ $ pacman -Q | grep xf86
lib32-libxxf86vm 1.1.3-1
libxxf86dga 1.1.4-1
libxxf86vm 1.1.3-1
xf86-input-evdev 2.8.2-1
xf86-input-wacom 0.23.0-1
xf86-video-intel 2.21.14-2
xf86dgaproto 2.1-2
xf86vidmodeproto 2.3.1-2

I already tried downgrading xf86-video-intel to xf86-video-intel-2.21.14-2.

It is hard for me to tell what is causing this issue. Is it related to X, systemd or dbus or something else?
This task depends upon

Closed by  Allan McRae (Allan)
Thursday, 02 January 2014, 05:13 GMT
Reason for closing:  Not a bug
Additional comments about closing:  Hardware limitation: "I was able to resolve the lagging behaviour of non-GTK apps. I found out that non-GTK apps were not lagging on Cinnamon or Gnome because these DEs use compositing. After enabling compton on Openbox, the lagging behaviour stops."
Comment by Robert Orzanna (orschiro) - Saturday, 07 December 2013, 12:18 GMT
Can this maybe be caused by some GTK or gconf settings being falsely set or missing and thus cannot be read by Qt apps?

Loading...