Hi !
I enabled a greater debug level. It seems that cups try to write to a
client while the connection is already closed.
Here the log before the crash :
Returning IPP successful-ok for Get-Job-Attributes
(ipp://fichdc:631/printers/AL-C3800_cdi) from 172.16.1.23
Here the full log concerning the connection con=0x7f8861d6c8f0 that made
the crash.
Baptiste.
** Attachment added: cups_write_bug.txt
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/512220/+attachment/4124153/+files/cups_write_bug.txt
--
You received this bug notification because you
I think that I understand more precisely the bug. I will comment the above log
where the client make two request :
- It request the printer attributes
and next
- the job attributes
The first request works, the second crash.
###
The first request
###
1) The client query
Hi,
@Johannes and Daniel
Maybe we can search what we have in common ?
1) Are your printers shared upon multiple printer servers ? (windows
2003, debian linux in my case)
2) Do you use a special authentification system ? (samba4 winbind in my
case)
I attach the log of two recent bugs if it can
@johannes:
Why do you thinks about a logrotate problem ? In my case, the last crash
happened 2 hours after to log have been rotated.
The last job :
AL-M7000_prof user1 247 [24/Mar/2014:09:10:07 +0100] 1 1 - 172.16.1.15 TF
etude - -
AL-M7000_prof user1 248 [24/Mar/2014:09:10:26 +0100] 1 1 -
Hi,
Same problem on Debian Wheezy with cups 1.5.3. So it is not a ubuntu
specific issue.
There is no need to access cups by http to reproduce the problem. For me
sending a job can produce the crash.
Thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
