Print protocol dies unexpectedly

[Alessio Medici]

On Thu, 05 Jun 2003, Michael Goffioul wrote:
> > Here is the backtrace:
> >=20
> > ----------- Backtrace begin ---------------
> >=20
> > Program received signal SIGSEGV, Segmentation fault.
> > 0x40c536e9 in QMutex::unlock() () from /opt/qt/lib/libqt-mt.so.3
> > (gdb) bt
> > #0  0x40c536e9 in QMutex::unlock() () from /opt/qt/lib/libqt-mt.so.3
> > #1  0x40967d9b in QEventLoop::processEvents(unsigned) ()
> >    from /opt/qt/lib/libqt-mt.so.3
> > #2  0x409c28f0 in QEventLoop::processEvents(unsigned, int) ()
> >    from /opt/qt/lib/libqt-mt.so.3
> > #3  0x409aee70 in QApplication::processEvents(int) ()
> >    from /opt/qt/lib/libqt-mt.so.3
> > #4  0x409aee37 in QApplication::processEvents() ()
> >    from /opt/qt/lib/libqt-mt.so.3
> > #5  0x41643a65 in KMCupsManager::completePrinterShort(KMPrinter*) ()
> >    from /opt/kde-3.1.2/lib/kde3/kdeprint_cups.so
>=20
> This part of code has been removed from the current CVS. So a recent
> CVS code should not produce the error anymore. It was actually a very
> ugly hack that is no avoided.

I have tried to install the KDE snapshot 20030606 and the problem disappe=
ared.
(Then I reinstalled KDE 3.1.2 because other applications were too unstabl=
e)

Thank you very much for your help.

Alessio