https://bugs.kde.org/show_bug.cgi?id=457370
--- Comment #3 from David Chmelik <dchme...@gmail.com> --- Confirmed: more parts (than taskbar) or KDE in general: following test script soon apparently (waited maybe one-half hour) permanently halted KDE (within few minutes no I/O despite barely 10% or fewer CPU (water-cooled overclocked) resources used entire time--not enough parallel processing(!)--and only a few programs placed windows) but worked so perfectly/quickly in XFCE (so clearly optimization/parallelism rather than hardware problem) I use there to save great deal time/effort starting daily programs. I was able to <CTRL><TAB><F1> out of KDE but not <CTRL><TAB><F11> back in except only to see KDE's terminal output/errors: KDE couldn't even redraw (in at least two separate tests). I would've put it before rest of my comment in code block section but don't see you have formatting/mark(up|down) documented here. I'm willing to test more soon/eventually (maybe today) but was enthusiastic about KDE3 as were most KDE user scientists/programmers, whom almost all preferred older KDEB,1,2,3 (when I only knew twm) and whom most I know haven't used it maybe 15 years... it's bugs like this (and other crash/major/grave/criticals even 15 years back untested then falsely marked 'intentional') made me lose all enthusiasm and now most trust/faith that power users/programmers will even be equally considered... I could go on about dozens/hundreds aspects but that'd be best for forum.kde.org . #!/bin/sh dolphin 1>/dev/null 2>&1& kate 1>/dev/null 2>&1& mcomix 1>/dev/null 2>&1& okular 1>/dev/null 2>&1& xmms 1>/dev/null 2>&1& birdtray 1>/dev/null 2>&1& pan 1>/dev/null 2>&1& hexchat 1>/dev/null 2>&1& pidgin 1>/dev/null 2>&1& palemoon-bin 1>/dev/null 2>&1& firefox 1>/dev/null 2>&1& chromium 1>/dev/null 2>&1& element 1>/dev/null 2>&1& discord 1>/dev/null 2>&1& slack 1>/dev/null 2>&1& skypeforlinux 1>/dev/null 2>&1& transmission 1>/dev/null 2>&1& nicotine 1>/dev/null 2>&1& eiskaltdcpp-qt 1/dev/null 2&1& -- You are receiving this mail because: You are watching all bug changes.
