Am Sunday 02 January 2011 schrieb Cyrille Berger Skott: > exiting. I would be more leaning toward a ktorrent bug than anything else. There's probably none, he set "ulimit -n 1" (that means: max amout of open file handles: "1" - since _everything_ on unix is a file, this is an instant* crasher as at least the X11 socket needs to be connected, kde applications use dbus -> 'nother socket, maybe you want to open a config file? icons? files to actually operate on? ...) - i think it was supposed to prove the weird "sth. in KDE uses sockets and that slows down my system because i've a lame HDD" idea, what is -as thiago pointed- bullsh... "nonsense" ;-)
*try "ulimit -n 1; ls; ulimit -n 1024" -> ls fails... @Herman If you figure the Oxygen style is slower than others on your system that is _for sure_ because of animations/ARGB pixmaps/you've got an nvidia GPU which /hates/ the QPixmap::fill(Qt:transparent) call... -> use the raster engine or switch to another style or help Hugo lowering the amount of ARGB pixmap allocations. Your HDD issues are not related here. KDE has the ksmserver socket and kdeinit4 + klauncher and khtml if you run konqueror - and there's of course dbus & X11, but that's rather not slowing down at runtime, becuse i doubt that any application continuosly bangs their inodes - the strategy is to connect once and then stay like this. Ifffffff there's a relation between running KDE applications and HDD issues i'd look after the pixmap cache (and your tempfs setup...) or the debug output (~/.xsession-errors) Thomas >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
