KDE 3.2's KProcess broke k3b?

Andras Mantia amantia at kde.org
Fri Feb 6 20:21:51 GMT 2004


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Already reported and the conclusion was that K3B is declared broken. Update 
K3b and it will work (although I have problems with data cd copy in the 
newest version). Alternatively search the archive to find the patch needed 
for K3b.

Andras

On Friday 06 February 2004 21:40, Matthias Welwarsky wrote:
> Hi,
>
> Don't nail me for this, but I think k3b broke due to the latest KProcess
> changes. Since I updated to KDE3.2 (SuSE RPMs, so it may be a packaging
> problem), K3B fails (at least when burning on-the-fly) because mkisofs
> fails while writing the iso image to stdout:
>
> /usr/bin/mkisofs: Resource temporarily unavailable. cannot fwrite 2048*1
>
> It looks like mkisofs get's a -EAGAIN while writing to stdout. Common
> situation when writing into a nonblocking socket or pipe, but mkisofs does
> not get along with it, because it assumes blocking behaviour (which is
> totally OK because stdout normally is blocking).
>
> Ossi? Want to look into this?
>
> regards,
> 	matthias

- -- 
Quanta Plus developer - http://quanta.sourceforge.net
K Desktop Environment - http://www.kde.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2-rc1-SuSE (GNU/Linux)

iD8DBQFAI/dfTQdfac6L/08RAvMAAJ4uNmGJPRWtTNKlqlw14zC+KOWEiwCfb1lg
7leXLP06LTVPHPgCGTceEhY=
=RcB2
-----END PGP SIGNATURE-----




More information about the kde-core-devel mailing list