Re: kprinter in KDE 3.1.1 crashes under sid
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Sunday 23 Mar 2003 03:40, Oliver Johns wrote:
> The crashes that Pablo di Vincente saw under woody also happen in a
> totally current (as of 2003.03.22) sid system. This was also an
> upgrade from 3.1.0. When one types kprinter from a konsole window
> the kprinter comes up and then instantly crashes with the message
>
> kdecore (KSocket): ERROR: KExtendedSocket::connectionEvent() called
> but no data available!
>
> The KDE crash dialog says that kprinter crashed with signal 11
> SIGSEGV.
>
> One way to postpone the crash is to remove the file
> ~/.kde/share/config/kdeprintrc
> Then the kprinter window will launch successfully. If you click on
> any option EXCEPT cups, the window will stay. But if you click on
> the CUPS option, there is an instant crash, as described above.
> I surmise that the trouble is when kprinter talks to cups.
>
> But, my cups is working fine. I can print to cups using the bsd
> compatibility commands like lp or lpr. That works with no glitch.
>
> I tried purging kdeprint and re-installing it after a reboot. That
> did not help. That suggests that kprinter interacts with files from
> some other package in 3.1.1 in some bad way.
>
> Ideas?
I cannot confirm this bug on a sid system which has seen most if not all
kde3 debs since 3.0.4-ish. I use CUPS and kprinter daily without
problem.
Paul Cupis
- --
paul@cupis.co.uk
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
iD8DBQE+fajPIzuKV+SHX/kRAt8tAJ9gES9+IERVQitEhKaWmtKSUBCHCgCeJ005
YTelazCiirkXygGVqoTGj2o=
=SSS8
-----END PGP SIGNATURE-----
Reply to: