Checked out why my remote konsole (over wifi) on one of the servers is so sluggish and found the konsole is constantly using about 0.7 MB/s bandwidth for the screen updates. The setup is: Server: Fedora 21 (dag) X- Client: Mageia 5 over WiFi (eseries) Startup command: ssh dag dbus-launch --exit-with-session konsole --display eseries:0.0 The command I am running in the console is nethogs I have set the option QT_GRAPHICSSYSTEM=native on remote connections a long time ago as QT_GRAPHICSSYSTEM=raster makes everything very sluggish on remote connections. Reproducible: Always Steps to Reproduce: 1. Start up remote console 2. Start nethogs in the window 3. Check out the bandwidth use Actual Results: Bandwidth usage is 700+ kB/s Expected Results: A lot lower BW usage
Just "upgraded" to FC23 and got konsole v. 15.08.3 on KDE 5.17.0 (Qt 5.5.1) and now this problem is even worse - A lot worse.. The same procedure as described above will consume ALL the bandwith of my WiFi for one simple konsole window. Come on guys, you are putting far too much effort into Wayland neglecting the current X-window remote user...
Is this issue still relevant?
Sure is. But it seems to be by design and concerns ALL remote KDE windows. Stopped using konsole in favour of lxterminal. That still works the way X-window was designed to work. A shame that the KDE people decided to go this route...
Qt no longer uses X11 calls to render text, it sends rendered bitmaps.
Exactly. The most stupid design decision ever...
Never complain until you tried to do better.
Have been involved in a lot of open source projects since 1985 or so and also in the start of Qt so I think I am entitled to critisize this regression, and quite heavily so....