| 2006-05-29 09:33:05 |
Daniel Brownlees |
description |
The recent upload of the final cups 1.2.0 has brougth the issue described in [1] up. Quick overview: kdeprint has been using private cups APIs, and those APIs have finally been removed in cups 1.2.0, breaking kdeprint (manifests as being unable to use TCP printing for me).
There seem to be patches available, and in kde svn apparently, though I'm not entirely sure which ones apply. See kde bugs [2]#115891 and [3]#124157. Seems likely to be fixed for 3.5.3, though again I haven't done enough research to be sure.
1. http://lists.quaker.eu.org/pipermail/kdedevelopers-feed/2006-April/000312.html
2. http://bugs.kde.org/show_bug.cgi?id=115891
3. http://bugs.kde.org/show_bug.cgi?id=124157 |
The recent upload of the final cups 1.2.0 has brought the issue described in [1] up. Quick overview: kdeprint has been using private cups APIs, and those APIs have finally been removed in cups 1.2.0, breaking kdeprint (manifests as being unable to use TCP printing for me).
There seem to be patches available, and in kde svn apparently, though I'm not entirely sure which ones apply. See kde bugs [2]#115891 and [3]#124157. Seems likely to be fixed for 3.5.3, though again I haven't done enough research to be sure.
1. http://lists.quaker.eu.org/pipermail/kdedevelopers-feed/2006-April/000312.html
2. http://bugs.kde.org/show_bug.cgi?id=115891
3. http://bugs.kde.org/show_bug.cgi?id=124157 |
|
