On Monday 03 January 2011 10:08:40 you wrote: > On Monday 03 January 2011, you wrote: > > I have disk problem (raid5 with hdd with hardware problem). But that's not > > influance gnome. > > > > But it's not connected to sockets. Sockets don't write to disk. -> > > partially wrong, the inode is writed to the disk, (after hardreboot some > > socket can be found on some folder), no disk acces to communication, but > > for connection > > (http://files.first-world.info/qt-project/unix-socket-relay-src.tar.bz2) > > > > I try without success profile application with gbd + ctrl c to find where > > it block. > > If creating a inode is creating a harddisk problem, I have question how you > expect to be able to download a file with ktorrent. But more to the point, > you > have not explain why you think oxygen is creating a socket. Because my behaviour is: loop { full hdd bandwith (1s), IO disk blocking durring 5s. } I have see the blocking problem at socket connection, and I have see KDE use lot of socket. With plastique theme I have less lag. With simple application (example into Qt creator), with theme oxygen I have lag. It's possible it's not socket my problem, but disk have direct influance to qt/kde widget.
> > > > I would be more leaning toward a ktorrent bug than anything else. > > > > I have choice ktorrent, but I can do this bug with kmail, kopete, plasma, > > dolphin, konqueror, ... > With the same backtrace ? I find that very unlikely... so it is probably a > different bug. That said, most applications that are closed with an open > dialog are going to crash. But that has nothing to do with socket or oxygen. > so it is probably a different bug. I think that's too now. -- alpha_one_x86 <alpha_one_...@first-world.info> Main developer of Ultracopier, Esourcing and server management IT, OS, technologies, security and business department
signature.asc
Description: This is a digitally signed message part.
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
