12 окт. 2015 г. 16:27 пользователь "Remco" <[email protected]> написал: > > After an upgrade to OpenBSD 5.8 the konsole application in KDE4 starts taking > 100% cpu when piping somethine through more/less, e.g.: > $ getent passwd |less > > I got some very basic output by running konsole as follows (from another > konsole window): > $ konsole > /tmp/konsole.log 2>&1 > > The logged information looks like: > > konsole:/usr/lib/libstdc++.so.57.0: /usr/local/lib/libestdc++.so.17.0 : WARNING: symbol(_ZN11__gnu_debug17_S_debug_messagesE) size mismatch, relink your program > QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave. > QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave. > konsole(21654) OpenBSDProcessInfo::readProcArgs: sysctl() call failed with code 3 > konsole(21654) OpenBSDProcessInfo::readCurrentDir: sysctl() call failed with code 3 > konsole(21654) OpenBSDProcessInfo::readProcArgs: sysctl() call failed with code 3 > konsole(21654) OpenBSDProcessInfo::readCurrentDir: sysctl() call failed with code 3 > konsole(21654) OpenBSDProcessInfo::readProcArgs: sysctl() call failed with code 3 > konsole(21654) OpenBSDProcessInfo::readCurrentDir: sysctl() call failed with code 3 > > with the last two messages appearing to repeat endlessly. > > The looping konsole can still be "stopped" by closing it's window. > After some time a popup will appear saying something along the lines of "the > application doesn't respond" giving the option to terminate it.
Thank you for the report. I've got a similar one, but failed trying to repeat it. Now I have some additional info, hope to resolve issue soon. It looks like the Konsole ignores ESRCH and tries to enlist the given process again and again... -- Vadim Zhukov -- Vadim Zhukov
