kio_giobridge IO slave

nf2 nf2 at
Mon Jan 7 15:41:03 GMT 2008

Thiago Macieira wrote:
> Vlad Codrea wrote:
>>> Since it is an additional/optional IO slave, it can just be
>>> deactivated/removed if it causes problems and the usual IO slave
>>> will be
>>> used.
>> Not really, because once distros are forced to link QtCore to Glib,
>> then all Qt and KDE apps will have to link to Glib and run on Glib's
>> non-native and slow event loop.
> You missed the point.
> If a user is experiencing errors with some ioslaves, the first thing that 
> would be recommended is to disable the giobridge. That would make KDE 
> apps use only native ioslaves. If the problem goes away, it's either GIO 
> or the bridge. If it persists, it's a native ioslave.

Not sure if people who use the giobridge will want the "native" KDE 
slaves to be reactivated. Perhaps this support problem could be solved 
with a tool which lists the protocols and who handles them.


More information about the kde-core-devel mailing list