Summary: | Simple remote Konsole window using huge amount of bandwidth | ||
---|---|---|---|
Product: | [Applications] konsole | Reporter: | dag |
Component: | general | Assignee: | Konsole Developer <konsole-devel> |
Status: | RESOLVED UPSTREAM | ||
Severity: | normal | CC: | cpigat242, notuxius |
Priority: | NOR | ||
Version: | 2.14.2 | ||
Target Milestone: | --- | ||
Platform: | Fedora RPMs | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
dag
2015-08-04 09:43:03 UTC
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.... |