In CUPS 1.2.11 this problem is fixed (CUPS version of current Gutsy).
On older versions it is recommended to set up print queues with the
TCP/Socket protocol. So modify the queue to use the Socket protocol. If
needed, use the printer's web interface to activate Socket support in
the printer.
**
I have had the same problem for quite a while, it seems like the cause
is the same as Bram Metsch. Unfortunately, i cannot apply the fix
provided in the STR you linked, so i am hoping to find a workaround. Is
there any way to sanitize a document before it's passed to IPP?
--
ipp jobs not purged;
We watch this problem especially if the title of the printed document conatins
an umlaut.
Maybe this Cups STR describes the problem:
http://www.cups.org/str.php?L1837
--
ipp jobs not purged; purging causes 100% cpu usage
https://bugs.launchpad.net/bugs/43352
You received this bug notification be
Curiously, I get no response from the snmp command, despite the fact
that lpstat sees the hp1200
[EMAIL PROTECTED]:~$ sudo /usr/lib/cups/backend-available/snmp 192.168.1.2
INFO: Using default SNMP Community public
[EMAIL PROTECTED]:~$ sudo /usr/lib/cups/backend-available/snmp
INFO: Using default
The problem maybe caused by bugs in the printer's implementation of IPP.
However my printer worked perfectly well using IPP under breezy. I get
this bug on dapper though (see my previous posts in the bug report - Bug
#43352). So I guess the http backend program changed in such a way that
it didn't
result of the snmp backend fyi:
[EMAIL PROTECTED]:~# /usr/lib/cups/backend-available/snmp
INFO: Using default SNMP Address @LOCAL
INFO: Using default SNMP Community public
network ipp://xxx.xxx.xxx.xxx:631/ipp "HP Color LaserJet 4550" "HP Color
LaserJet 4550 xxx.xxx.xxx.xxx"
"MFG:Hewlett-Packard
It recommends IPP, but that's most likely because the printers have lpd
and tck disabled to prevent abuse.
They're all network printers, so sockets are no option. If the problem
persists i might switch to using ldp, but it's not preffered.
Just one question: does the snmp backend in feisty also w
Probably the problem is caused by bugs in the printer's implementation
of IPP, so as long as upstream CUPS does not do a work-around in their
IPP backend, the best is to use one of the other communication protocol
of the printer.
Can everyone of you who reported the problem with printing via IPP r
No, unfortunately this is a live system. I'd guess it would be fixed in
feisty, but we're not just ready yet to upgrade our server.
It will be replaced in a few months or so, so i'm hoping it's fixed in
edgy.
--
ipp jobs not purged; purging causes 100% cpu usage
https://launchpad.net/bugs/43352
Can you boot with a Feisty live CD and see whether the problem occurs
there?
--
ipp jobs not purged; purging causes 100% cpu usage
https://launchpad.net/bugs/43352
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
We are encountering the following bug as well. Every now and then 2 ipp
processes keep running on the cups server and eating 100% cpu time.
Stracing the processes show the following:
recvfrom(4, "", 2048, 0, NULL, NULL)= 0
time(NULL) = 1173275152
recvfrom(4, "", 2
Hi Peter,
I'm not sure who is waiting for what. The bug is (still) here. I'd be
more than happy to provide more info but it seems no one is listening?
brgds,
Jan
Peter Cherriman wrote:
> What info are we waiting for on this bug?
>
> I'm seeing effectively the same problem.
>
> My printer is con
What info are we waiting for on this bug?
I'm seeing effectively the same problem.
My printer is connected via parallel port and via the ethernet port on
the printer.
If I send a job via the IPP protocol directly to the printer's EpsonNet
interface, the job prints but is never removed from the p
I have the same problem. Although I do not experience the high cpu
amount, I do have a job lingering in the print job window after job
completion. When I cancel the job and a new job was issued, the new job
is finally printed. Please fix this because it is a bit annoying to have
a job printed upon
I can confirm these findings. Printing from Ubuntu Dapper to a HP PSC950
connected via USB and a print server with ipp. Are there any more
requests for additional information?
--
ipp jobs not purged; purging causes 100% cpu usage
https://launchpad.net/bugs/43352
--
ubuntu-bugs mailing list
ubun
Jouni,
I think you maybe confusing matters.
I think the initial reporter and myself are talking about sending jobs
to network printers using the IPP protocol.
I have a printer connect via parallel and ethernet to my dapper machine.
The parallel port queue works perfectly, the other queue (ipp vi
> My friend have laserjet 1200 connected with paraller port. The > problem he
> has might be wrong permissions of
> /etc/cups/cups.d/ports.conf or something like that.
Solved with updates? or/and changing permissions and cupsys restart
--
ipp jobs not purged; purging causes 100% cpu usage
ht
My friend have laserjet 1200 connected with paraller port. The problem
he has might be wrong permissions of /etc/cups/cups.d/ports.conf or
something like that.
--
ipp jobs not purged; purging causes 100% cpu usage
https://launchpad.net/bugs/43352
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ub
Ante Karamatić wrote:
> What versions of CUPS are on printer server?
>
dpkg -l | grep cupsys
ii cupsys 1.2.2-0ubuntu0.6.06Common
UNIX Printing System(tm) - server
ii cupsys-bsd 1.2.2-0ubuntu0.6.06Common
UNIX Printing System
What versions of CUPS are on printer server?
--
ipp jobs not purged; purging causes 100% cpu usage
https://launchpad.net/bugs/43352
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
I getting almost the exactly the same problem since I've upgraded from
breezy to dapper.
I've also noticed that once a constant amount of network traffic between
the printer and the ubuntu PC which continues until I kill the processes
owned by cupsys printing for user pjc.
http://192.168.1.201:63
Ante Karamatić wrote:
> You are missing:
>
> Listen /var/run/cups/cups.sock
>
> in /etc/cups/cups.d/ports.conf
>
> Could you please add that, restart CUPS and try again? Thanks.
>
I am afraid there is no change in behavior
TRS
--
ipp jobs not purged; purging causes 100% cpu usage
https://la
You are missing:
Listen /var/run/cups/cups.sock
in /etc/cups/cups.d/ports.conf
Could you please add that, restart CUPS and try again? Thanks.
--
ipp jobs not purged; purging causes 100% cpu usage
https://launchpad.net/bugs/43352
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https:/
** Changed in: cupsys (Ubuntu)
Assignee: trshemanske => (unassigned)
--
ipp jobs not purged; purging causes 100% cpu usage
https://launchpad.net/bugs/43352
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
24 matches
Mail list logo
